nix-update-source 0 -> 1 attrpath: nix-update-source Checking auto update branch... [version] [version] skipping because derivation has updateScript [rustCrateVersion] [rustCrateVersion] No cargoSha256 or cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] Failed with exit code 1 these 20 derivations will be built: /nix/store/4slrqs2m9laa3q6h59yyiwz1bqw0p5dp-python3.10-flask-limiter-3.3.1.drv /nix/store/66q1w9qxw441cy5ryywil6qa3lybbid9-python3.10-httpbin-0.7.0.drv /nix/store/v3in4ic4rygmaf8lhm0yhwv84bwc4z8d-python3.10-pytest-httpbin-1.0.2.drv /nix/store/d8cnx3wjmjyw8yqfspsq08hdh6d2i8gx-python3.10-httpcore-0.17.2.drv /nix/store/0n9vras6wp3gnfggns0qi2w0z8p3wfs1-python3.10-httpx-0.24.1.drv /nix/store/zvs5hryz4457g9i9yyv9wjyc3nm2wdfs-python3.10-starlette-0.27.0.drv /nix/store/4mg924dx3y5g1gf4iagwgf7br6020vlh-python3.10-fastapi-0.95.2.drv /nix/store/99abrnjggcyc6fqqqbmz4fndf3fnxkyf-python3.10-mocket-3.11.0.drv /nix/store/6n00xfrq85znawka0ab0vzqd62dpgj7z-python3.10-geoip2-4.7.0.drv /nix/store/r4nqpn2nvz9h0jwrzndjrz5vsb55ijy2-python3.10-Django-4.2.5.drv /nix/store/pmq79nila8y4m8yzwnjblxf6zgi1rw5w-python3.10-factory-boy-3.3.0.drv /nix/store/1644v1yqzzg66f88y08ppz5ajnxa88pm-python3.10-pytest-randomly-3.13.0.drv /nix/store/81q5zh3i7ivm31qyq334l0lz6k850pza-python3.10-httplib2-0.21.0.drv /nix/store/q357fi619w1nxrlziij8ns16bniywfw6-python3.10-lazr.restfulclient-0.14.5.drv /nix/store/vnnxj0jhdbx0f891lmd181clq6ypph1y-python3.10-launchpadlib-1.11.0.drv /nix/store/rv60cgr1fn5ykkrjqf06mbs7078wcbzr-python3.10-breezy-3.3.4.drv /nix/store/9y1r4gl4gm9gg95pjq2dggrz307yhda6-nix-prefetch-bzr.drv /nix/store/cncmaasrjpw0v28c6jmvrl7rakzynjlp-nix-prefetch-scripts.drv /nix/store/32l4axiw5r9wzp65d8jlj0dj5n070hf4-nix-update-source-0.6.3.drv /nix/store/g3b55d2lq74xf112a0p15aki99qclsb6-packages.json.drv these 5 paths will be fetched (0.55 MiB download, 4.08 MiB unpacked): /nix/store/1lg4lkmf96x666f8rbv0a8am5pmyakgn-python3.10-markdown-it-py-2.2.0 /nix/store/lkyvmgrsmazgrv0m2x3fxi06afd3fj96-python3.10-multipart-0.2.4 /nix/store/zk9bfzi49gw5fkjga0rzx4kp68mc6gmk-python3.10-rich-13.3.5 /nix/store/6s7c6zn2d67f4pc145hlzzqqd1fd6cq9-python3.10-trustme-1.1.0 /nix/store/m5rkcg11xnqk1pfcxcp9rikmdkrz7lw5-python3.10-uvicorn-0.23.1 copying path '/nix/store/lkyvmgrsmazgrv0m2x3fxi06afd3fj96-python3.10-multipart-0.2.4' from 'https://cache.nixos.org'... copying path '/nix/store/6s7c6zn2d67f4pc145hlzzqqd1fd6cq9-python3.10-trustme-1.1.0' from 'https://cache.nixos.org'... copying path '/nix/store/m5rkcg11xnqk1pfcxcp9rikmdkrz7lw5-python3.10-uvicorn-0.23.1' from 'https://cache.nixos.org'... copying path '/nix/store/1lg4lkmf96x666f8rbv0a8am5pmyakgn-python3.10-markdown-it-py-2.2.0' from 'https://cache.nixos.org'... copying path '/nix/store/zk9bfzi49gw5fkjga0rzx4kp68mc6gmk-python3.10-rich-13.3.5' from 'https://cache.nixos.org'... building '/nix/store/4slrqs2m9laa3q6h59yyiwz1bqw0p5dp-python3.10-flask-limiter-3.3.1.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/gm79cq6zpij8vf0gicymmv1m7il4q1x5-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/versioneer.py patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/flask_limiter copying flask_limiter/__init__.py -> build/lib/flask_limiter copying flask_limiter/manager.py -> build/lib/flask_limiter copying flask_limiter/_compat.py -> build/lib/flask_limiter copying flask_limiter/_version.py -> build/lib/flask_limiter copying flask_limiter/typing.py -> build/lib/flask_limiter copying flask_limiter/extension.py -> build/lib/flask_limiter copying flask_limiter/wrappers.py -> build/lib/flask_limiter copying flask_limiter/constants.py -> build/lib/flask_limiter copying flask_limiter/commands.py -> build/lib/flask_limiter copying flask_limiter/version.py -> build/lib/flask_limiter copying flask_limiter/errors.py -> build/lib/flask_limiter copying flask_limiter/util.py -> build/lib/flask_limiter creating build/lib/flask_limiter/contrib copying flask_limiter/contrib/util.py -> build/lib/flask_limiter/contrib copying flask_limiter/contrib/__init__.py -> build/lib/flask_limiter/contrib running egg_info creating Flask_Limiter.egg-info writing Flask_Limiter.egg-info/PKG-INFO writing dependency_links to Flask_Limiter.egg-info/dependency_links.txt writing entry points to Flask_Limiter.egg-info/entry_points.txt writing requirements to Flask_Limiter.egg-info/requires.txt writing top-level names to Flask_Limiter.egg-info/top_level.txt writing manifest file 'Flask_Limiter.egg-info/SOURCES.txt' reading manifest file 'Flask_Limiter.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE.txt' writing manifest file 'Flask_Limiter.egg-info/SOURCES.txt' copying flask_limiter/py.typed -> build/lib/flask_limiter UPDATING build/lib/flask_limiter/_version.py set build/lib/flask_limiter/_version.py to '3.3.1' /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/extension.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/_version.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/_compat.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/manager.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/util.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/__init__.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/typing.py -> build/bdist.linux-x86_64/wheel/flask_limiter creating build/bdist.linux-x86_64/wheel/flask_limiter/contrib copying build/lib/flask_limiter/contrib/__init__.py -> build/bdist.linux-x86_64/wheel/flask_limiter/contrib copying build/lib/flask_limiter/contrib/util.py -> build/bdist.linux-x86_64/wheel/flask_limiter/contrib copying build/lib/flask_limiter/py.typed -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/version.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/constants.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/errors.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/wrappers.py -> build/bdist.linux-x86_64/wheel/flask_limiter copying build/lib/flask_limiter/commands.py -> build/bdist.linux-x86_64/wheel/flask_limiter running install_egg_info Copying Flask_Limiter.egg-info to build/bdist.linux-x86_64/wheel/Flask_Limiter-3.3.1-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/Flask_Limiter-3.3.1.dist-info/WHEEL creating 'dist/Flask_Limiter-3.3.1-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'flask_limiter/__init__.py' adding 'flask_limiter/_compat.py' adding 'flask_limiter/_version.py' adding 'flask_limiter/commands.py' adding 'flask_limiter/constants.py' adding 'flask_limiter/errors.py' adding 'flask_limiter/extension.py' adding 'flask_limiter/manager.py' adding 'flask_limiter/py.typed' adding 'flask_limiter/typing.py' adding 'flask_limiter/util.py' adding 'flask_limiter/version.py' adding 'flask_limiter/wrappers.py' adding 'flask_limiter/contrib/__init__.py' adding 'flask_limiter/contrib/util.py' adding 'Flask_Limiter-3.3.1.dist-info/LICENSE.txt' adding 'Flask_Limiter-3.3.1.dist-info/METADATA' adding 'Flask_Limiter-3.3.1.dist-info/WHEEL' adding 'Flask_Limiter-3.3.1.dist-info/entry_points.txt' adding 'Flask_Limiter-3.3.1.dist-info/top_level.txt' adding 'Flask_Limiter-3.3.1.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed Flask_Limiter-3.3.1-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/i0dkh434fqznrrdj6k37xby516b04wyf-python3.10-flask-limiter-3.3.1 checking for references to /build/ in /nix/store/i0dkh434fqznrrdj6k37xby516b04wyf-python3.10-flask-limiter-3.3.1... patching script interpreter paths in /nix/store/i0dkh434fqznrrdj6k37xby516b04wyf-python3.10-flask-limiter-3.3.1 stripping (with command strip and flags -S -p) in /nix/store/i0dkh434fqznrrdj6k37xby516b04wyf-python3.10-flask-limiter-3.3.1/lib shrinking RPATHs of ELF executables and libraries in /nix/store/mh14c0hdp0lmzxrm5djx608dvqb8j3jd-python3.10-flask-limiter-3.3.1-dist checking for references to /build/ in /nix/store/mh14c0hdp0lmzxrm5djx608dvqb8j3jd-python3.10-flask-limiter-3.3.1-dist... patching script interpreter paths in /nix/store/mh14c0hdp0lmzxrm5djx608dvqb8j3jd-python3.10-flask-limiter-3.3.1-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: flask_limiter pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 -- /nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 cachedir: .pytest_cache rootdir: /build/source configfile: pytest.ini plugins: mock-3.11.1 collected 118 items / 13 deselected / 105 selected tests/test_blueprints.py::test_blueprint PASSED tests/test_blueprints.py::test_blueprint_limit_with_route_limits PASSED tests/test_blueprints.py::test_nested_blueprint_exemption_explicit PASSED tests/test_blueprints.py::test_nested_blueprint_exemption_legacy PASSED tests/test_blueprints.py::test_nested_blueprint_exemption_nested PASSED tests/test_blueprints.py::test_nested_blueprint_exemption_ridiculous PASSED tests/test_blueprints.py::test_nested_blueprint_exemption_child_only PASSED tests/test_blueprints.py::test_nested_blueprint_child_explicit_limit PASSED tests/test_blueprints.py::test_nested_blueprint_child_explicit_nested_limits PASSED tests/test_blueprints.py::test_register_blueprint PASSED tests/test_blueprints.py::test_invalid_decorated_static_limit_blueprint PASSED tests/test_blueprints.py::test_invalid_decorated_dynamic_limits_blueprint PASSED tests/test_commands.py::test_no_limiter PASSED tests/test_commands.py::test_config PASSED tests/test_commands.py::test_no_config PASSED tests/test_commands.py::test_limits PASSED tests/test_commands.py::test_limits_filter_endpoint PASSED tests/test_commands.py::test_limits_filter_path PASSED tests/test_commands.py::test_limits_with_test PASSED tests/test_commands.py::test_limits_with_test_storage_down PASSED tests/test_configuration.py::test_invalid_strategy PASSED tests/test_configuration.py::test_invalid_storage_string PASSED tests/test_configuration.py::test_header_names_config PASSED tests/test_configuration.py::test_header_names_constructor PASSED tests/test_configuration.py::test_invalid_config_with_disabled PASSED tests/test_configuration.py::test_uninitialized_limiter PASSED tests/test_context_manager.py::test_static_limit PASSED tests/test_context_manager.py::test_dynamic_limits PASSED tests/test_context_manager.py::test_scoped_context_manager PASSED tests/test_decorators.py::test_multiple_decorators PASSED tests/test_decorators.py::test_exempt_routes PASSED tests/test_decorators.py::test_decorated_limit_with_scope PASSED tests/test_decorators.py::test_decorated_limit_with_conditional_deduction PASSED tests/test_decorators.py::test_shared_limit_with_conditional_deduction PASSED tests/test_decorators.py::test_header_ordering_with_conditional_deductions PASSED tests/test_decorators.py::test_decorated_limits_with_combined_defaults PASSED tests/test_decorators.py::test_decorated_limit_with_combined_defaults_per_method PASSED tests/test_decorators.py::test_decorated_dynamic_limits PASSED tests/test_decorators.py::test_invalid_decorated_dynamic_limits PASSED tests/test_decorators.py::test_decorated_limit_empty_exempt PASSED tests/test_decorators.py::test_invalid_decorated_static_limits PASSED tests/test_decorators.py::test_named_shared_limit PASSED tests/test_decorators.py::test_dynamic_shared_limit PASSED tests/test_decorators.py::test_conditional_limits PASSED tests/test_decorators.py::test_conditional_shared_limits PASSED tests/test_decorators.py::test_whitelisting PASSED tests/test_decorators.py::test_separate_method_limits PASSED tests/test_decorators.py::test_explicit_method_limits PASSED tests/test_decorators.py::test_decorated_limit_immediate PASSED tests/test_decorators.py::test_decorated_shared_limit_immediate PASSED tests/test_decorators.py::test_async_route PASSED tests/test_decorators.py::test_on_breach_callback_swallow_errors PASSED tests/test_decorators.py::test_on_breach_callback_custom_response PASSED tests/test_decorators.py::test_limit_multiple_cost PASSED tests/test_decorators.py::test_limit_multiple_cost_callable PASSED tests/test_decorators.py::test_shared_limit_multiple_cost PASSED tests/test_decorators.py::test_shared_limit_multiple_cost_callable PASSED tests/test_decorators.py::test_non_route_decoration_static_limits_override_defaults PASSED tests/test_decorators.py::test_non_route_decoration_static_limits PASSED tests/test_decorators.py::test_non_route_decoration_dynamic_limits PASSED tests/test_decorators.py::test_non_route_decoration_multiple_sequential_limits_per_request PASSED tests/test_decorators.py::test_inner_function_decoration PASSED tests/test_error_handling.py::test_error_message PASSED tests/test_error_handling.py::test_custom_error_message PASSED tests/test_error_handling.py::test_swallow_error PASSED tests/test_error_handling.py::test_swallow_error_conditional_deduction PASSED tests/test_error_handling.py::test_no_swallow_error PASSED tests/test_error_handling.py::test_no_swallow_error_conditional_deduction PASSED tests/test_flask_ext.py::test_reset PASSED tests/test_flask_ext.py::test_combined_rate_limits PASSED tests/test_flask_ext.py::test_defaults_per_method PASSED tests/test_flask_ext.py::test_default_limit_with_exemption PASSED tests/test_flask_ext.py::test_default_limit_with_variable_cost PASSED tests/test_flask_ext.py::test_default_limit_with_conditional_deduction PASSED tests/test_flask_ext.py::test_key_func PASSED tests/test_flask_ext.py::test_logging PASSED tests/test_flask_ext.py::test_reuse_logging PASSED tests/test_flask_ext.py::test_disabled_flag PASSED tests/test_flask_ext.py::test_multiple_apps PASSED tests/test_flask_ext.py::test_headers_no_breach PASSED tests/test_flask_ext.py::test_headers_application_limits PASSED tests/test_flask_ext.py::test_headers_breach PASSED tests/test_flask_ext.py::test_retry_after PASSED tests/test_flask_ext.py::test_retry_after_exists_seconds PASSED tests/test_flask_ext.py::test_retry_after_exists_rfc1123 PASSED tests/test_flask_ext.py::test_custom_headers_from_config PASSED tests/test_flask_ext.py::test_application_shared_limit PASSED tests/test_flask_ext.py::test_callable_default_limit PASSED tests/test_flask_ext.py::test_callable_application_limit PASSED tests/test_flask_ext.py::test_no_auto_check PASSED tests/test_flask_ext.py::test_no_auto_check_custom_before_request PASSED tests/test_flask_ext.py::test_fail_on_first_breach PASSED tests/test_flask_ext.py::test_no_fail_on_first_breach PASSED tests/test_flask_ext.py::test_default_on_breach_callback PASSED tests/test_flask_ext.py::test_multiple_instances_no_key_prefix PASSED tests/test_flask_ext.py::test_independent_instances_by_key_prefix PASSED tests/test_flask_ext.py::test_multiple_limiters_default_limits PASSED tests/test_regressions.py::test_dynamic_limits PASSED tests/test_regressions.py::test_invalid_ratelimit_key PASSED tests/test_regressions.py::test_default_limits_with_per_route_limit PASSED tests/test_regressions.py::test_application_limits_from_config PASSED tests/test_regressions.py::test_endpoint_with_dot_but_not_blueprint PASSED tests/test_views.py::test_pluggable_views PASSED tests/test_views.py::test_pluggable_method_views PASSED tests/test_views.py::test_flask_restx_resource XFAIL =============================== warnings summary =============================== tests/test_blueprints.py: 12 warnings tests/test_commands.py: 7 warnings tests/test_configuration.py: 3 warnings tests/test_context_manager.py: 3 warnings tests/test_decorators.py: 33 warnings tests/test_error_handling.py: 6 warnings tests/test_flask_ext.py: 28 warnings tests/test_regressions.py: 5 warnings tests/test_views.py: 2 warnings /build/source/flask_limiter/extension.py:293: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html =========================== short test summary info ============================ XFAIL tests/test_views.py::test_flask_restx_resource ========== 104 passed, 13 deselected, 1 xfailed, 99 warnings in 2.35s ========== Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/66q1w9qxw441cy5ryywil6qa3lybbid9-python3.10-httpbin-0.7.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/qhbvmap7zc9j1slskaxhiarr24z4zmvf-httpbin-0.7.0.tar.gz source root is httpbin-0.7.0 setting SOURCE_DATE_EPOCH to timestamp 1525780837 of file httpbin-0.7.0/setup.cfg patching sources applying patch /nix/store/dwzbw1y0jgv2nh2yiznxjfh4vqvpkqvm-5cc81ce87a3c447a127e4a1a707faf9f3b1c9b6b.patch patching file httpbin/core.py Hunk #1 succeeded at 19 with fuzz 2 (offset -10 lines). Hunk #2 succeeded at 48 with fuzz 1 (offset -29 lines). updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/httpbin copying httpbin/structures.py -> build/lib/httpbin copying httpbin/helpers.py -> build/lib/httpbin copying httpbin/core.py -> build/lib/httpbin copying httpbin/__init__.py -> build/lib/httpbin copying httpbin/utils.py -> build/lib/httpbin copying httpbin/filters.py -> build/lib/httpbin running egg_info writing httpbin.egg-info/PKG-INFO writing dependency_links to httpbin.egg-info/dependency_links.txt writing requirements to httpbin.egg-info/requires.txt writing top-level names to httpbin.egg-info/top_level.txt reading manifest file 'httpbin.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'README.rst' warning: no files found matching 'requirements.txt' adding license file 'LICENSE' adding license file 'AUTHORS' writing manifest file 'httpbin.egg-info/SOURCES.txt' /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'httpbin.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'httpbin.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'httpbin.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'httpbin.templates' to be distributed and are already explicitly excluding 'httpbin.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'httpbin.templates.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'httpbin.templates.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'httpbin.templates.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'httpbin.templates.images' to be distributed and are already explicitly excluding 'httpbin.templates.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/httpbin/templates copying httpbin/templates/UTF-8-demo.txt -> build/lib/httpbin/templates copying httpbin/templates/forms-post.html -> build/lib/httpbin/templates copying httpbin/templates/httpbin.1.html -> build/lib/httpbin/templates copying httpbin/templates/index.html -> build/lib/httpbin/templates copying httpbin/templates/moby.html -> build/lib/httpbin/templates copying httpbin/templates/sample.xml -> build/lib/httpbin/templates copying httpbin/templates/trackingscripts.html -> build/lib/httpbin/templates creating build/lib/httpbin/templates/images copying httpbin/templates/images/jackal.jpg -> build/lib/httpbin/templates/images copying httpbin/templates/images/pig_icon.png -> build/lib/httpbin/templates/images copying httpbin/templates/images/svg_logo.svg -> build/lib/httpbin/templates/images copying httpbin/templates/images/wolf_1.webp -> build/lib/httpbin/templates/images /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/httpbin copying build/lib/httpbin/structures.py -> build/bdist.linux-x86_64/wheel/httpbin copying build/lib/httpbin/core.py -> build/bdist.linux-x86_64/wheel/httpbin copying build/lib/httpbin/helpers.py -> build/bdist.linux-x86_64/wheel/httpbin copying build/lib/httpbin/__init__.py -> build/bdist.linux-x86_64/wheel/httpbin copying build/lib/httpbin/utils.py -> build/bdist.linux-x86_64/wheel/httpbin creating build/bdist.linux-x86_64/wheel/httpbin/templates copying build/lib/httpbin/templates/forms-post.html -> build/bdist.linux-x86_64/wheel/httpbin/templates copying build/lib/httpbin/templates/trackingscripts.html -> build/bdist.linux-x86_64/wheel/httpbin/templates copying build/lib/httpbin/templates/sample.xml -> build/bdist.linux-x86_64/wheel/httpbin/templates creating build/bdist.linux-x86_64/wheel/httpbin/templates/images copying build/lib/httpbin/templates/images/jackal.jpg -> build/bdist.linux-x86_64/wheel/httpbin/templates/images copying build/lib/httpbin/templates/images/pig_icon.png -> build/bdist.linux-x86_64/wheel/httpbin/templates/images copying build/lib/httpbin/templates/images/svg_logo.svg -> build/bdist.linux-x86_64/wheel/httpbin/templates/images copying build/lib/httpbin/templates/images/wolf_1.webp -> build/bdist.linux-x86_64/wheel/httpbin/templates/images copying build/lib/httpbin/templates/UTF-8-demo.txt -> build/bdist.linux-x86_64/wheel/httpbin/templates copying build/lib/httpbin/templates/moby.html -> build/bdist.linux-x86_64/wheel/httpbin/templates copying build/lib/httpbin/templates/index.html -> build/bdist.linux-x86_64/wheel/httpbin/templates copying build/lib/httpbin/templates/httpbin.1.html -> build/bdist.linux-x86_64/wheel/httpbin/templates copying build/lib/httpbin/filters.py -> build/bdist.linux-x86_64/wheel/httpbin running install_egg_info Copying httpbin.egg-info to build/bdist.linux-x86_64/wheel/httpbin-0.7.0-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/httpbin-0.7.0.dist-info/WHEEL creating 'dist/httpbin-0.7.0-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'httpbin/__init__.py' adding 'httpbin/core.py' adding 'httpbin/filters.py' adding 'httpbin/helpers.py' adding 'httpbin/structures.py' adding 'httpbin/utils.py' adding 'httpbin/templates/UTF-8-demo.txt' adding 'httpbin/templates/forms-post.html' adding 'httpbin/templates/httpbin.1.html' adding 'httpbin/templates/index.html' adding 'httpbin/templates/moby.html' adding 'httpbin/templates/sample.xml' adding 'httpbin/templates/trackingscripts.html' adding 'httpbin/templates/images/jackal.jpg' adding 'httpbin/templates/images/pig_icon.png' adding 'httpbin/templates/images/svg_logo.svg' adding 'httpbin/templates/images/wolf_1.webp' adding 'httpbin-0.7.0.dist-info/AUTHORS' adding 'httpbin-0.7.0.dist-info/LICENSE' adding 'httpbin-0.7.0.dist-info/METADATA' adding 'httpbin-0.7.0.dist-info/WHEEL' adding 'httpbin-0.7.0.dist-info/top_level.txt' adding 'httpbin-0.7.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed httpbin-0.7.0-py2.py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/19196rmq8flr29hplsp49dixgavcq8xs-python3.10-httpbin-0.7.0 checking for references to /build/ in /nix/store/19196rmq8flr29hplsp49dixgavcq8xs-python3.10-httpbin-0.7.0... patching script interpreter paths in /nix/store/19196rmq8flr29hplsp49dixgavcq8xs-python3.10-httpbin-0.7.0 stripping (with command strip and flags -S -p) in /nix/store/19196rmq8flr29hplsp49dixgavcq8xs-python3.10-httpbin-0.7.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/shr2avv0fqiic0g9sxl3gg6sx9bcbapj-python3.10-httpbin-0.7.0-dist checking for references to /build/ in /nix/store/shr2avv0fqiic0g9sxl3gg6sx9bcbapj-python3.10-httpbin-0.7.0-dist... patching script interpreter paths in /nix/store/shr2avv0fqiic0g9sxl3gg6sx9bcbapj-python3.10-httpbin-0.7.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: httpbin pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/httpbin-0.7.0 collected 63 items / 8 deselected / 55 selected test_httpbin.py ....................................................... [100%] =============================== warnings summary =============================== httpbin/helpers.py:26 /build/httpbin-0.7.0/httpbin/helpers.py:26: DeprecationWarning: invalid escape sequence '\_' ASCII_ART = """ httpbin/helpers.py:72 /build/httpbin-0.7.0/httpbin/helpers.py:72: DeprecationWarning: invalid escape sequence '\ ' ANGRY_ASCII =""" httpbin/helpers.py:439 /build/httpbin-0.7.0/httpbin/helpers.py:439: DeprecationWarning: invalid escape sequence '\s' match = re.search('\s*(W/)?\"?([^"]*)\"?\s*', part) -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ================= 55 passed, 8 deselected, 3 warnings in 5.89s ================= Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/v3in4ic4rygmaf8lhm0yhwv84bwc4z8d-python3.10-pytest-httpbin-1.0.2.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/1mhvbgyi9ldwpapicm14z235ddch3bhm-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tox.ini patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/pytest_httpbin copying pytest_httpbin/serve.py -> build/lib/pytest_httpbin copying pytest_httpbin/certs.py -> build/lib/pytest_httpbin copying pytest_httpbin/__init__.py -> build/lib/pytest_httpbin copying pytest_httpbin/version.py -> build/lib/pytest_httpbin copying pytest_httpbin/plugin.py -> build/lib/pytest_httpbin running egg_info creating pytest_httpbin.egg-info writing pytest_httpbin.egg-info/PKG-INFO writing dependency_links to pytest_httpbin.egg-info/dependency_links.txt writing entry points to pytest_httpbin.egg-info/entry_points.txt writing requirements to pytest_httpbin.egg-info/requires.txt writing top-level names to pytest_httpbin.egg-info/top_level.txt writing manifest file 'pytest_httpbin.egg-info/SOURCES.txt' reading manifest file 'pytest_httpbin.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'pytest_httpbin.egg-info/SOURCES.txt' /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pytest_httpbin.certs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pytest_httpbin.certs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pytest_httpbin.certs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pytest_httpbin.certs' to be distributed and are already explicitly excluding 'pytest_httpbin.certs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/pytest_httpbin/certs copying pytest_httpbin/certs/cacert.pem -> build/lib/pytest_httpbin/certs copying pytest_httpbin/certs/cert.pem -> build/lib/pytest_httpbin/certs copying pytest_httpbin/certs/key.pem -> build/lib/pytest_httpbin/certs /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/pytest_httpbin copying build/lib/pytest_httpbin/serve.py -> build/bdist.linux-x86_64/wheel/pytest_httpbin copying build/lib/pytest_httpbin/certs.py -> build/bdist.linux-x86_64/wheel/pytest_httpbin copying build/lib/pytest_httpbin/version.py -> build/bdist.linux-x86_64/wheel/pytest_httpbin creating build/bdist.linux-x86_64/wheel/pytest_httpbin/certs copying build/lib/pytest_httpbin/certs/key.pem -> build/bdist.linux-x86_64/wheel/pytest_httpbin/certs copying build/lib/pytest_httpbin/certs/cert.pem -> build/bdist.linux-x86_64/wheel/pytest_httpbin/certs copying build/lib/pytest_httpbin/certs/cacert.pem -> build/bdist.linux-x86_64/wheel/pytest_httpbin/certs copying build/lib/pytest_httpbin/plugin.py -> build/bdist.linux-x86_64/wheel/pytest_httpbin copying build/lib/pytest_httpbin/__init__.py -> build/bdist.linux-x86_64/wheel/pytest_httpbin running install_egg_info Copying pytest_httpbin.egg-info to build/bdist.linux-x86_64/wheel/pytest_httpbin-1.0.2-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/pytest_httpbin-1.0.2.dist-info/WHEEL creating 'dist/pytest_httpbin-1.0.2-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'pytest_httpbin/__init__.py' adding 'pytest_httpbin/certs.py' adding 'pytest_httpbin/plugin.py' adding 'pytest_httpbin/serve.py' adding 'pytest_httpbin/version.py' adding 'pytest_httpbin/certs/cacert.pem' adding 'pytest_httpbin/certs/cert.pem' adding 'pytest_httpbin/certs/key.pem' adding 'pytest_httpbin-1.0.2.dist-info/METADATA' adding 'pytest_httpbin-1.0.2.dist-info/WHEEL' adding 'pytest_httpbin-1.0.2.dist-info/entry_points.txt' adding 'pytest_httpbin-1.0.2.dist-info/top_level.txt' adding 'pytest_httpbin-1.0.2.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed pytest_httpbin-1.0.2-py2.py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/r6573n8d3gh28xpi5a3qwi4kr8wz6iz3-python3.10-pytest-httpbin-1.0.2 checking for references to /build/ in /nix/store/r6573n8d3gh28xpi5a3qwi4kr8wz6iz3-python3.10-pytest-httpbin-1.0.2... patching script interpreter paths in /nix/store/r6573n8d3gh28xpi5a3qwi4kr8wz6iz3-python3.10-pytest-httpbin-1.0.2 stripping (with command strip and flags -S -p) in /nix/store/r6573n8d3gh28xpi5a3qwi4kr8wz6iz3-python3.10-pytest-httpbin-1.0.2/lib shrinking RPATHs of ELF executables and libraries in /nix/store/r3kabgzpgbz8kh9am1bvkn45hiks9gxy-python3.10-pytest-httpbin-1.0.2-dist checking for references to /build/ in /nix/store/r3kabgzpgbz8kh9am1bvkn45hiks9gxy-python3.10-pytest-httpbin-1.0.2-dist... patching script interpreter paths in /nix/store/r3kabgzpgbz8kh9am1bvkn45hiks9gxy-python3.10-pytest-httpbin-1.0.2-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: pytest_httpbin pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/source plugins: httpbin-1.0.2 collected 20 items tests/test_httpbin.py ............. [ 65%] tests/test_server.py ....... [100%] =============================== warnings summary =============================== tests/test_httpbin.py: 14 warnings tests/test_server.py: 3 warnings /build/source/pytest_httpbin/serve.py:65: DeprecationWarning: ssl.wrap_socket() is deprecated, use SSLContext.wrap_socket() ssock = ssl.wrap_socket( tests/test_httpbin.py: 14 warnings tests/test_server.py: 3 warnings /nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib/python3.10/ssl.py:1434: DeprecationWarning: ssl.PROTOCOL_TLS is deprecated context = SSLContext(ssl_version) -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ======================= 20 passed, 34 warnings in 2.13s ======================== Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/d8cnx3wjmjyw8yqfspsq08hdh6d2i8gx-python3.10-httpcore-0.17.2.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/srvdv01q9p5n1br66nzqlymn4bynbgix-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/unasync.py patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/httpcore copying httpcore/_models.py -> build/lib/httpcore copying httpcore/_synchronization.py -> build/lib/httpcore copying httpcore/__init__.py -> build/lib/httpcore copying httpcore/_exceptions.py -> build/lib/httpcore copying httpcore/_trace.py -> build/lib/httpcore copying httpcore/_utils.py -> build/lib/httpcore copying httpcore/_ssl.py -> build/lib/httpcore copying httpcore/_api.py -> build/lib/httpcore creating build/lib/httpcore/backends copying httpcore/backends/trio.py -> build/lib/httpcore/backends copying httpcore/backends/base.py -> build/lib/httpcore/backends copying httpcore/backends/auto.py -> build/lib/httpcore/backends copying httpcore/backends/__init__.py -> build/lib/httpcore/backends copying httpcore/backends/sync.py -> build/lib/httpcore/backends copying httpcore/backends/asyncio.py -> build/lib/httpcore/backends copying httpcore/backends/mock.py -> build/lib/httpcore/backends creating build/lib/httpcore/_async copying httpcore/_async/connection_pool.py -> build/lib/httpcore/_async copying httpcore/_async/interfaces.py -> build/lib/httpcore/_async copying httpcore/_async/socks_proxy.py -> build/lib/httpcore/_async copying httpcore/_async/__init__.py -> build/lib/httpcore/_async copying httpcore/_async/connection.py -> build/lib/httpcore/_async copying httpcore/_async/http2.py -> build/lib/httpcore/_async copying httpcore/_async/http_proxy.py -> build/lib/httpcore/_async copying httpcore/_async/http11.py -> build/lib/httpcore/_async creating build/lib/httpcore/_sync copying httpcore/_sync/interfaces.py -> build/lib/httpcore/_sync copying httpcore/_sync/connection_pool.py -> build/lib/httpcore/_sync copying httpcore/_sync/__init__.py -> build/lib/httpcore/_sync copying httpcore/_sync/socks_proxy.py -> build/lib/httpcore/_sync copying httpcore/_sync/connection.py -> build/lib/httpcore/_sync copying httpcore/_sync/http2.py -> build/lib/httpcore/_sync copying httpcore/_sync/http11.py -> build/lib/httpcore/_sync copying httpcore/_sync/http_proxy.py -> build/lib/httpcore/_sync running egg_info creating httpcore.egg-info writing httpcore.egg-info/PKG-INFO writing dependency_links to httpcore.egg-info/dependency_links.txt writing requirements to httpcore.egg-info/requires.txt writing top-level names to httpcore.egg-info/top_level.txt writing manifest file 'httpcore.egg-info/SOURCES.txt' reading manifest file 'httpcore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE.md' writing manifest file 'httpcore.egg-info/SOURCES.txt' copying httpcore/py.typed -> build/lib/httpcore /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/httpcore copying build/lib/httpcore/_api.py -> build/bdist.linux-x86_64/wheel/httpcore copying build/lib/httpcore/_models.py -> build/bdist.linux-x86_64/wheel/httpcore copying build/lib/httpcore/_ssl.py -> build/bdist.linux-x86_64/wheel/httpcore copying build/lib/httpcore/_trace.py -> build/bdist.linux-x86_64/wheel/httpcore creating build/bdist.linux-x86_64/wheel/httpcore/backends copying build/lib/httpcore/backends/asyncio.py -> build/bdist.linux-x86_64/wheel/httpcore/backends copying build/lib/httpcore/backends/__init__.py -> build/bdist.linux-x86_64/wheel/httpcore/backends copying build/lib/httpcore/backends/trio.py -> build/bdist.linux-x86_64/wheel/httpcore/backends copying build/lib/httpcore/backends/base.py -> build/bdist.linux-x86_64/wheel/httpcore/backends copying build/lib/httpcore/backends/auto.py -> build/bdist.linux-x86_64/wheel/httpcore/backends copying build/lib/httpcore/backends/sync.py -> build/bdist.linux-x86_64/wheel/httpcore/backends copying build/lib/httpcore/backends/mock.py -> build/bdist.linux-x86_64/wheel/httpcore/backends creating build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/connection_pool.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/socks_proxy.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/http11.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/connection.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/http2.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/__init__.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/http_proxy.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/_sync/interfaces.py -> build/bdist.linux-x86_64/wheel/httpcore/_sync copying build/lib/httpcore/__init__.py -> build/bdist.linux-x86_64/wheel/httpcore copying build/lib/httpcore/py.typed -> build/bdist.linux-x86_64/wheel/httpcore copying build/lib/httpcore/_synchronization.py -> build/bdist.linux-x86_64/wheel/httpcore copying build/lib/httpcore/_utils.py -> build/bdist.linux-x86_64/wheel/httpcore creating build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/__init__.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/interfaces.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/http11.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/connection_pool.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/http2.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/socks_proxy.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/connection.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_async/http_proxy.py -> build/bdist.linux-x86_64/wheel/httpcore/_async copying build/lib/httpcore/_exceptions.py -> build/bdist.linux-x86_64/wheel/httpcore running install_egg_info Copying httpcore.egg-info to build/bdist.linux-x86_64/wheel/httpcore-0.17.2-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/httpcore-0.17.2.dist-info/WHEEL creating 'dist/httpcore-0.17.2-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'httpcore/__init__.py' adding 'httpcore/_api.py' adding 'httpcore/_exceptions.py' adding 'httpcore/_models.py' adding 'httpcore/_ssl.py' adding 'httpcore/_synchronization.py' adding 'httpcore/_trace.py' adding 'httpcore/_utils.py' adding 'httpcore/py.typed' adding 'httpcore/_async/__init__.py' adding 'httpcore/_async/connection.py' adding 'httpcore/_async/connection_pool.py' adding 'httpcore/_async/http11.py' adding 'httpcore/_async/http2.py' adding 'httpcore/_async/http_proxy.py' adding 'httpcore/_async/interfaces.py' adding 'httpcore/_async/socks_proxy.py' adding 'httpcore/_sync/__init__.py' adding 'httpcore/_sync/connection.py' adding 'httpcore/_sync/connection_pool.py' adding 'httpcore/_sync/http11.py' adding 'httpcore/_sync/http2.py' adding 'httpcore/_sync/http_proxy.py' adding 'httpcore/_sync/interfaces.py' adding 'httpcore/_sync/socks_proxy.py' adding 'httpcore/backends/__init__.py' adding 'httpcore/backends/asyncio.py' adding 'httpcore/backends/auto.py' adding 'httpcore/backends/base.py' adding 'httpcore/backends/mock.py' adding 'httpcore/backends/sync.py' adding 'httpcore/backends/trio.py' adding 'httpcore-0.17.2.dist-info/LICENSE.md' adding 'httpcore-0.17.2.dist-info/METADATA' adding 'httpcore-0.17.2.dist-info/WHEEL' adding 'httpcore-0.17.2.dist-info/top_level.txt' adding 'httpcore-0.17.2.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed httpcore-0.17.2-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/gsn7ha4660mlh8vhvgba4v3g7i0gjagm-python3.10-httpcore-0.17.2 checking for references to /build/ in /nix/store/gsn7ha4660mlh8vhvgba4v3g7i0gjagm-python3.10-httpcore-0.17.2... patching script interpreter paths in /nix/store/gsn7ha4660mlh8vhvgba4v3g7i0gjagm-python3.10-httpcore-0.17.2 stripping (with command strip and flags -S -p) in /nix/store/gsn7ha4660mlh8vhvgba4v3g7i0gjagm-python3.10-httpcore-0.17.2/lib shrinking RPATHs of ELF executables and libraries in /nix/store/jlamr6xb2h7rbjlpmh1dlq1a4namylpz-python3.10-httpcore-0.17.2-dist checking for references to /build/ in /nix/store/jlamr6xb2h7rbjlpmh1dlq1a4namylpz-python3.10-httpcore-0.17.2-dist... patching script interpreter paths in /nix/store/jlamr6xb2h7rbjlpmh1dlq1a4namylpz-python3.10-httpcore-0.17.2-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: httpcore pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/source plugins: asyncio-0.21.1, httpbin-1.0.2, trio-0.7.0, anyio-3.7.1 asyncio: mode=strict collected 187 items tests/test_api.py .127.0.0.1 - - [29/Sep/2023 08:08:46] "GET / HTTP/1.1" 200 12142 .. [ 1%] tests/test_models.py ............. [ 8%] tests/_async/test_connection.py .............. [ 16%] tests/_async/test_connection_pool.py ............................. [ 31%] tests/_async/test_http11.py ........................ [ 44%] tests/_async/test_http2.py .................... [ 55%] tests/_async/test_http_proxy.py .......... [ 60%] tests/_async/test_integration.py ...... [ 63%] tests/_async/test_socks_proxy.py .......... [ 68%] tests/_sync/test_connection.py ....... [ 72%] tests/_sync/test_connection_pool.py ................ [ 81%] tests/_sync/test_http11.py ............ [ 87%] tests/_sync/test_http2.py .......... [ 93%] tests/_sync/test_http_proxy.py ..... [ 95%] tests/_sync/test_integration.py ... [ 97%] tests/_sync/test_socks_proxy.py ..... [100%] =============================== warnings summary =============================== tests/_async/test_connection.py::test_http_connection[trio] /nix/store/6737dhv1z2r9rnzbmwqgknz44kx1y3zj-python3.10-anyio-3.7.1/lib/python3.10/site-packages/anyio/_backends/_trio.py:162: TrioDeprecationWarning: trio.MultiError is deprecated since Trio 0.22.0; use BaseExceptionGroup (on Python 3.11 and later) or exceptiongroup.BaseExceptionGroup (earlier versions) instead (https://github.com/python-trio/trio/issues/2211) class ExceptionGroup(BaseExceptionGroup, trio.MultiError): tests/_async/test_integration.py::test_ssl_request[asyncio] tests/_async/test_integration.py::test_ssl_request[trio] tests/_async/test_integration.py::test_extra_info[asyncio] tests/_async/test_integration.py::test_extra_info[trio] tests/_sync/test_integration.py::test_ssl_request tests/_sync/test_integration.py::test_extra_info /nix/store/r6573n8d3gh28xpi5a3qwi4kr8wz6iz3-python3.10-pytest-httpbin-1.0.2/lib/python3.10/site-packages/pytest_httpbin/serve.py:65: DeprecationWarning: ssl.wrap_socket() is deprecated, use SSLContext.wrap_socket() ssock = ssl.wrap_socket( tests/_async/test_integration.py::test_ssl_request[asyncio] tests/_async/test_integration.py::test_ssl_request[trio] tests/_async/test_integration.py::test_extra_info[asyncio] tests/_async/test_integration.py::test_extra_info[trio] tests/_sync/test_integration.py::test_ssl_request tests/_sync/test_integration.py::test_extra_info /nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib/python3.10/ssl.py:1434: DeprecationWarning: ssl.PROTOCOL_TLS is deprecated context = SSLContext(ssl_version) -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ======================= 187 passed, 13 warnings in 9.87s ======================= Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/0n9vras6wp3gnfggns0qi2w0z8p3wfs1-python3.10-httpx-0.24.1.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing pytest-check-hook Using pytestCheckPhase unpacking sources unpacking source archive /nix/store/5baccqlk3vjyjck4y88zkyasbyrca843-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tests/test_wsgi.py patching sources substituteStream(): WARNING: pattern 'rfc3986[idna2008]>=1.3,<2' doesn't match anything in file 'pyproject.toml' updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing pypaBuildPhase Creating a wheel... * Getting build dependencies for wheel... * Building wheel... Successfully built httpx-0.24.1-py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase installing Executing pypaInstallPhase Successfully installed httpx-0.24.1-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/f7k4pa92202ir27p0anj2nxdppac085y-python3.10-httpx-0.24.1 checking for references to /build/ in /nix/store/f7k4pa92202ir27p0anj2nxdppac085y-python3.10-httpx-0.24.1... patching script interpreter paths in /nix/store/f7k4pa92202ir27p0anj2nxdppac085y-python3.10-httpx-0.24.1 stripping (with command strip and flags -S -p) in /nix/store/f7k4pa92202ir27p0anj2nxdppac085y-python3.10-httpx-0.24.1/lib /nix/store/f7k4pa92202ir27p0anj2nxdppac085y-python3.10-httpx-0.24.1/bin shrinking RPATHs of ELF executables and libraries in /nix/store/ac2sq5vdly9pxxnx652f52nmaf2gxv7z-python3.10-httpx-0.24.1-dist checking for references to /build/ in /nix/store/ac2sq5vdly9pxxnx652f52nmaf2gxv7z-python3.10-httpx-0.24.1-dist... patching script interpreter paths in /nix/store/ac2sq5vdly9pxxnx652f52nmaf2gxv7z-python3.10-httpx-0.24.1-dist Rewriting #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 to #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12 wrapping `/nix/store/f7k4pa92202ir27p0anj2nxdppac085y-python3.10-httpx-0.24.1/bin/httpx'... Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: httpx pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/source configfile: pyproject.toml plugins: asyncio-0.21.1, trio-0.7.0, anyio-3.7.1 asyncio: mode=strict collected 816 items / 5 deselected / 811 selected tests/test_api.py ........... [ 1%] tests/test_asgi.py .................... [ 3%] tests/test_auth.py .... [ 4%] tests/test_config.py ............................... [ 8%] tests/test_content.py ........................................ [ 13%] tests/test_decoders.py .................................. [ 17%] tests/test_exceptions.py ... [ 17%] tests/test_exported_members.py . [ 17%] tests/test_multipart.py ...................................... [ 22%] tests/test_status_codes.py ...... [ 23%] tests/test_timeouts.py ...... [ 23%] tests/test_urlparse.py ................................... [ 28%] tests/test_utils.py .................................................... [ 34%] .. [ 34%] tests/test_wsgi.py ........... [ 36%] tests/client/test_async_client.py ...................................... [ 40%] .............. [ 42%] tests/client/test_auth.py ............s................................. [ 48%] ................................... [ 52%] tests/client/test_client.py ................................... [ 56%] tests/client/test_cookies.py ....... [ 57%] tests/client/test_event_hooks.py ......... [ 58%] tests/client/test_headers.py ........... [ 60%] tests/client/test_properties.py ........ [ 61%] tests/client/test_proxies.py ........................................... [ 66%] ............................. [ 70%] tests/client/test_queryparams.py ... [ 70%] tests/client/test_redirects.py ............................... [ 74%] tests/models/test_cookies.py ....... [ 75%] tests/models/test_headers.py .................. [ 77%] tests/models/test_queryparams.py .............. [ 79%] tests/models/test_requests.py ....................... [ 81%] tests/models/test_responses.py ......................................... [ 87%] ................................................................ [ 94%] tests/models/test_url.py ......................................... [100%] =========================== short test summary info ============================ SKIPPED [1] tests/client/test_auth.py:272: netrc files without a password are invalid with Python < 3.11 ================ 810 passed, 1 skipped, 5 deselected in 15.46s ================= Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/zvs5hryz4457g9i9yyv9wjyc3nm2wdfs-python3.10-starlette-0.27.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing pytest-check-hook Using pytestCheckPhase unpacking sources unpacking source archive /nix/store/d68vc14wlfj9wjgglx7k2hqbkykc88l1-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tests/test_websockets.py patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing pypaBuildPhase Creating a wheel... * Getting build dependencies for wheel... * Building wheel... Successfully built starlette-0.27.0-py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase installing Executing pypaInstallPhase Successfully installed starlette-0.27.0-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/7rjd1p0sfbaxiyzkml4h649zrjyjpxm1-python3.10-starlette-0.27.0 checking for references to /build/ in /nix/store/7rjd1p0sfbaxiyzkml4h649zrjyjpxm1-python3.10-starlette-0.27.0... patching script interpreter paths in /nix/store/7rjd1p0sfbaxiyzkml4h649zrjyjpxm1-python3.10-starlette-0.27.0 stripping (with command strip and flags -S -p) in /nix/store/7rjd1p0sfbaxiyzkml4h649zrjyjpxm1-python3.10-starlette-0.27.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/nc9mjqkdwkylrjpmgx1gw57s5dpjv08h-python3.10-starlette-0.27.0-dist checking for references to /build/ in /nix/store/nc9mjqkdwkylrjpmgx1gw57s5dpjv08h-python3.10-starlette-0.27.0-dist... patching script interpreter paths in /nix/store/nc9mjqkdwkylrjpmgx1gw57s5dpjv08h-python3.10-starlette-0.27.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: starlette pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/source configfile: setup.cfg plugins: anyio-3.7.1 collected 680 items / 4 deselected / 676 selected tests/test__utils.py ...... [ 0%] tests/test_applications.py ............................................. [ 7%] ... [ 7%] tests/test_authentication.py ........... [ 9%] tests/test_background.py ........ [ 10%] tests/test_concurrency.py .... [ 11%] tests/test_config.py .... [ 11%] tests/test_convertors.py ...... [ 12%] tests/test_datastructures.py .......................... [ 16%] tests/test_endpoints.py .................... [ 19%] tests/test_exceptions.py ................. [ 22%] tests/test_formparsers.py .............................................. [ 28%] ...................... [ 32%] tests/test_requests.py ................................................. [ 39%] .................. [ 42%] tests/test_responses.py ................................................ [ 49%] .............. [ 51%] tests/test_routing.py .................................................. [ 58%] ............................. [ 63%] tests/test_schemas.py ... [ 63%] tests/test_staticfiles.py .............................................. [ 70%] ...... [ 71%] tests/test_status.py .. [ 71%] tests/test_templates.py ....... [ 72%] tests/test_testclient.py ....................... [ 75%] tests/test_websockets.py ............................................... [ 82%] .............. [ 84%] tests/middleware/test_base.py .........x.x........ [ 87%] tests/middleware/test_cors.py .............................. [ 92%] tests/middleware/test_errors.py ............ [ 94%] tests/middleware/test_gzip.py .......... [ 95%] tests/middleware/test_https_redirect.py .. [ 95%] tests/middleware/test_middleware.py . [ 96%] tests/middleware/test_session.py ............ [ 97%] tests/middleware/test_trusted_host.py ..... [ 98%] tests/middleware/test_wsgi.py .......... [100%] =========================== short test summary info ============================ XFAIL tests/middleware/test_base.py::test_contextvars[asyncio-CustomMiddlewareUsingBaseHTTPMiddleware] - BaseHTTPMiddleware creates a TaskGroup which copies the contextand erases any changes to it made within the TaskGroup XFAIL tests/middleware/test_base.py::test_contextvars[trio-CustomMiddlewareUsingBaseHTTPMiddleware] - BaseHTTPMiddleware creates a TaskGroup which copies the contextand erases any changes to it made within the TaskGroup ================ 674 passed, 4 deselected, 2 xfailed in 19.60s ================= Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/4mg924dx3y5g1gf4iagwgf7br6020vlh-python3.10-fastapi-0.95.2.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing pytest-check-hook Using pytestCheckPhase unpacking sources unpacking source archive /nix/store/ls9n9qvarcmm8x88awip2ig6nsyvb13i-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tests/utils.py patching sources substituteStream(): WARNING: pattern 'starlette==' doesn't match anything in file 'pyproject.toml' updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing pypaBuildPhase Creating a wheel... * Getting build dependencies for wheel... * Building wheel... Successfully built fastapi-0.95.2-py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase installing Executing pypaInstallPhase Successfully installed fastapi-0.95.2-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/qbpkq57s6x3k5fjqx0q65d9k4vyymf90-python3.10-fastapi-0.95.2 checking for references to /build/ in /nix/store/qbpkq57s6x3k5fjqx0q65d9k4vyymf90-python3.10-fastapi-0.95.2... patching script interpreter paths in /nix/store/qbpkq57s6x3k5fjqx0q65d9k4vyymf90-python3.10-fastapi-0.95.2 stripping (with command strip and flags -S -p) in /nix/store/qbpkq57s6x3k5fjqx0q65d9k4vyymf90-python3.10-fastapi-0.95.2/lib shrinking RPATHs of ELF executables and libraries in /nix/store/90s6q5vd7rfdlry1m8jrdysni3bwibdy-python3.10-fastapi-0.95.2-dist checking for references to /build/ in /nix/store/90s6q5vd7rfdlry1m8jrdysni3bwibdy-python3.10-fastapi-0.95.2-dist... patching script interpreter paths in /nix/store/90s6q5vd7rfdlry1m8jrdysni3bwibdy-python3.10-fastapi-0.95.2-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: fastapi pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/source configfile: pyproject.toml plugins: anyio-3.7.1, asyncio-0.21.1, devtools-0.11.0 asyncio: mode=strict collected 1879 items / 78 deselected / 1801 selected tests/test_additional_properties.py .. [ 0%] tests/test_additional_response_extra.py .. [ 0%] tests/test_additional_responses_bad.py . [ 0%] tests/test_additional_responses_custom_model_in_callback.py . [ 0%] tests/test_additional_responses_custom_validationerror.py . [ 0%] tests/test_additional_responses_default_validationerror.py . [ 0%] tests/test_additional_responses_response_class.py . [ 0%] tests/test_additional_responses_router.py ..... [ 0%] tests/test_ambiguous_params.py .. [ 0%] tests/test_annotated.py ............. [ 1%] tests/test_application.py ........ [ 2%] tests/test_callable_endpoint.py . [ 2%] tests/test_custom_middleware_exception.py .. [ 2%] tests/test_custom_route_class.py ..... [ 2%] tests/test_custom_schema_fields.py .. [ 2%] tests/test_custom_swagger_ui_redirect.py ... [ 2%] tests/test_datastructures.py .... [ 2%] tests/test_datetime_custom_encoder.py . [ 3%] tests/test_default_response_class_router.py .............. [ 3%] tests/test_dependency_cache.py .... [ 4%] tests/test_dependency_class.py ........ [ 4%] tests/test_dependency_contextmanager.py ...................... [ 5%] tests/test_dependency_contextvars.py . [ 5%] tests/test_dependency_duplicates.py ..... [ 6%] tests/test_dependency_normal_exceptions.py .. [ 6%] tests/test_dependency_overrides.py ................................ [ 7%] tests/test_dependency_security_overrides.py ... [ 8%] tests/test_deprecated_openapi_prefix.py .. [ 8%] tests/test_duplicate_models_openapi.py .. [ 8%] tests/test_empty_router.py .. [ 8%] tests/test_enforce_once_required_parameter.py ... [ 8%] tests/test_exception_handlers.py .... [ 8%] tests/test_extra_routes.py ..... [ 9%] tests/test_filter_pydantic_sub_model.py ... [ 9%] tests/test_forms_from_non_typing_sequences.py ... [ 9%] tests/test_generate_unique_id_function.py ....... [ 9%] tests/test_get_request_body.py .. [ 9%] tests/test_http_connection_injection.py .. [ 10%] tests/test_include_route.py . [ 10%] tests/test_include_router_defaults_overrides.py ........................ [ 11%] ................... [ 12%] tests/test_infer_param_optionality.py .......... [ 13%] tests/test_inherited_custom_class.py . [ 13%] tests/test_invalid_path_param.py ....... [ 13%] tests/test_invalid_sequence_param.py .... [ 13%] tests/test_jsonable_encoder.py ................. [ 14%] tests/test_local_docs.py ..... [ 14%] tests/test_multi_body_errors.py .... [ 15%] tests/test_multi_query_errors.py ... [ 15%] tests/test_multipart_installation.py .......... [ 15%] tests/test_no_swagger_ui_redirect.py ... [ 16%] tests/test_openapi_query_parameter_extension.py .. [ 16%] tests/test_openapi_route_extensions.py .. [ 16%] tests/test_openapi_servers.py .. [ 16%] tests/test_operations_signatures.py . [ 16%] tests/test_orjson_response_class.py . [ 16%] tests/test_param_class.py .. [ 16%] tests/test_param_in_path_and_dependency.py .. [ 16%] tests/test_param_include_in_schema.py ........ [ 17%] tests/test_params_repr.py ...................... [ 18%] tests/test_path.py ..................................................... [ 21%] ...................... [ 22%] tests/test_put_no_body.py ... [ 22%] tests/test_query.py ......................... [ 24%] tests/test_read_with_orm_mode.py . [ 24%] tests/test_repeated_cookie_headers.py . [ 24%] tests/test_repeated_dependency_schema.py .. [ 24%] tests/test_repeated_parameter_alias.py .. [ 24%] tests/test_reponse_set_reponse_code_empty.py .. [ 24%] tests/test_request_body_parameters_media_type.py . [ 24%] tests/test_required_noneable.py ....... [ 24%] tests/test_response_by_alias.py .......... [ 25%] tests/test_response_change_status_code.py . [ 25%] tests/test_response_class_no_mediatype.py . [ 25%] tests/test_response_code_no_body.py .. [ 25%] tests/test_response_model_as_return_annotation.py ...................... [ 26%] ................ [ 27%] tests/test_response_model_include_exclude.py ...... [ 28%] tests/test_response_model_invalid.py .... [ 28%] tests/test_response_model_sub_types.py .. [ 28%] tests/test_route_scope.py ..... [ 28%] tests/test_router_events.py .. [ 28%] tests/test_router_prefix_with_template.py . [ 28%] tests/test_schema_extra_examples.py .. [ 29%] tests/test_security_api_key_cookie.py ... [ 29%] tests/test_security_api_key_cookie_description.py ... [ 29%] tests/test_security_api_key_cookie_optional.py ... [ 29%] tests/test_security_api_key_header.py ... [ 29%] tests/test_security_api_key_header_description.py ... [ 29%] tests/test_security_api_key_header_optional.py ... [ 30%] tests/test_security_api_key_query.py ... [ 30%] tests/test_security_api_key_query_description.py ... [ 30%] tests/test_security_api_key_query_optional.py ... [ 30%] tests/test_security_http_base.py ... [ 30%] tests/test_security_http_base_description.py ... [ 30%] tests/test_security_http_base_optional.py ... [ 31%] tests/test_security_http_basic_optional.py ..... [ 31%] tests/test_security_http_basic_realm.py ..... [ 31%] tests/test_security_http_basic_realm_description.py ..... [ 31%] tests/test_security_http_bearer.py .... [ 32%] tests/test_security_http_bearer_description.py .... [ 32%] tests/test_security_http_bearer_optional.py .... [ 32%] tests/test_security_http_digest.py .... [ 32%] tests/test_security_http_digest_description.py .... [ 33%] tests/test_security_http_digest_optional.py .... [ 33%] tests/test_security_oauth2.py ........ [ 33%] tests/test_security_oauth2_authorization_code_bearer.py .... [ 33%] tests/test_security_oauth2_authorization_code_bearer_description.py .... [ 34%] [ 34%] tests/test_security_oauth2_optional.py ........ [ 34%] tests/test_security_oauth2_optional_description.py ........ [ 35%] tests/test_security_oauth2_password_bearer_optional.py .... [ 35%] tests/test_security_oauth2_password_bearer_optional_description.py .... [ 35%] tests/test_security_openid_connect.py .... [ 35%] tests/test_security_openid_connect_description.py .... [ 35%] tests/test_security_openid_connect_optional.py .... [ 36%] tests/test_serialize_response.py ... [ 36%] tests/test_serialize_response_dataclass.py ....... [ 36%] tests/test_serialize_response_model.py ........ [ 37%] tests/test_skip_defaults.py ..... [ 37%] tests/test_starlette_exception.py ....... [ 37%] tests/test_starlette_urlconvertors.py ..... [ 38%] tests/test_sub_callbacks.py .. [ 38%] tests/test_swagger_ui_init_oauth.py .. [ 38%] tests/test_tuples.py ....... [ 38%] tests/test_typing_python39.py . [ 38%] tests/test_union_body.py ... [ 38%] tests/test_union_inherited_body.py ... [ 39%] tests/test_validate_response.py ...... [ 39%] tests/test_validate_response_dataclass.py ... [ 39%] tests/test_validate_response_recursive.py . [ 39%] tests/test_ws_router.py ........ [ 40%] tests/test_modules_same_name_body/test_main.py ..... [ 40%] tests/test_tutorial/test_additional_responses/test_tutorial001.py ... [ 40%] tests/test_tutorial/test_additional_responses/test_tutorial002.py ... [ 40%] tests/test_tutorial/test_additional_responses/test_tutorial003.py ... [ 40%] tests/test_tutorial/test_additional_responses/test_tutorial004.py ... [ 41%] tests/test_tutorial/test_additional_status_codes/test_tutorial001.py .. [ 41%] tests/test_tutorial/test_additional_status_codes/test_tutorial001_an.py . [ 41%] . [ 41%] tests/test_tutorial/test_additional_status_codes/test_tutorial001_an_py310.py . [ 41%] . [ 41%] tests/test_tutorial/test_additional_status_codes/test_tutorial001_an_py39.py . [ 41%] . [ 41%] tests/test_tutorial/test_additional_status_codes/test_tutorial001_py310.py . [ 41%] . [ 41%] tests/test_tutorial/test_advanced_middleware/test_tutorial001.py . [ 41%] tests/test_tutorial/test_advanced_middleware/test_tutorial002.py . [ 41%] tests/test_tutorial/test_advanced_middleware/test_tutorial003.py . [ 41%] tests/test_tutorial/test_async_tests/test_main.py .... [ 41%] tests/test_tutorial/test_background_tasks/test_tutorial001.py . [ 42%] tests/test_tutorial/test_background_tasks/test_tutorial002.py . [ 42%] tests/test_tutorial/test_background_tasks/test_tutorial002_an.py . [ 42%] tests/test_tutorial/test_background_tasks/test_tutorial002_an_py310.py . [ 42%] [ 42%] tests/test_tutorial/test_background_tasks/test_tutorial002_an_py39.py . [ 42%] tests/test_tutorial/test_background_tasks/test_tutorial002_py310.py . [ 42%] tests/test_tutorial/test_behind_a_proxy/test_tutorial001.py .. [ 42%] tests/test_tutorial/test_behind_a_proxy/test_tutorial002.py .. [ 42%] tests/test_tutorial/test_behind_a_proxy/test_tutorial003.py .. [ 42%] tests/test_tutorial/test_behind_a_proxy/test_tutorial004.py .. [ 42%] tests/test_tutorial/test_bigger_applications/test_main.py .............. [ 43%] ........... [ 44%] tests/test_tutorial/test_bigger_applications/test_main_an.py ........... [ 44%] .............. [ 45%] tests/test_tutorial/test_bigger_applications/test_main_an_py39.py ...... [ 45%] ................... [ 46%] tests/test_tutorial/test_body/test_tutorial001.py ................ [ 47%] tests/test_tutorial/test_body/test_tutorial001_py310.py ................ [ 48%] [ 48%] tests/test_tutorial/test_body_fields/test_tutorial001.py .... [ 48%] tests/test_tutorial/test_body_fields/test_tutorial001_an.py .... [ 49%] tests/test_tutorial/test_body_fields/test_tutorial001_an_py310.py .... [ 49%] tests/test_tutorial/test_body_fields/test_tutorial001_an_py39.py .... [ 49%] tests/test_tutorial/test_body_fields/test_tutorial001_py310.py .... [ 49%] tests/test_tutorial/test_body_multiple_params/test_tutorial001.py ..... [ 50%] tests/test_tutorial/test_body_multiple_params/test_tutorial001_an.py ... [ 50%] .. [ 50%] tests/test_tutorial/test_body_multiple_params/test_tutorial001_an_py310.py . [ 50%] .... [ 50%] tests/test_tutorial/test_body_multiple_params/test_tutorial001_an_py39.py . [ 50%] .... [ 50%] tests/test_tutorial/test_body_multiple_params/test_tutorial001_py310.py . [ 50%] .... [ 51%] tests/test_tutorial/test_body_multiple_params/test_tutorial003.py .... [ 51%] tests/test_tutorial/test_body_multiple_params/test_tutorial003_an.py ... [ 51%] . [ 51%] tests/test_tutorial/test_body_multiple_params/test_tutorial003_an_py310.py . [ 51%] ... [ 51%] tests/test_tutorial/test_body_multiple_params/test_tutorial003_an_py39.py . [ 51%] ... [ 52%] tests/test_tutorial/test_body_multiple_params/test_tutorial003_py310.py . [ 52%] ... [ 52%] tests/test_tutorial/test_body_nested_models/test_tutorial009.py ... [ 52%] tests/test_tutorial/test_body_nested_models/test_tutorial009_py39.py ... [ 52%] [ 52%] tests/test_tutorial/test_body_updates/test_tutorial001.py ... [ 52%] tests/test_tutorial/test_body_updates/test_tutorial001_py310.py ... [ 52%] tests/test_tutorial/test_body_updates/test_tutorial001_py39.py ... [ 53%] tests/test_tutorial/test_conditional_openapi/test_tutorial001.py ... [ 53%] tests/test_tutorial/test_cookie_params/test_tutorial001.py ..... [ 53%] tests/test_tutorial/test_cookie_params/test_tutorial001_an.py ..... [ 53%] tests/test_tutorial/test_cookie_params/test_tutorial001_an_py310.py .... [ 54%] . [ 54%] tests/test_tutorial/test_cookie_params/test_tutorial001_an_py39.py ..... [ 54%] [ 54%] tests/test_tutorial/test_cookie_params/test_tutorial001_py310.py ..... [ 54%] tests/test_tutorial/test_cors/test_tutorial001.py . [ 54%] tests/test_tutorial/test_custom_request_and_route/test_tutorial001.py .. [ 54%] . [ 54%] tests/test_tutorial/test_custom_request_and_route/test_tutorial002.py .. [ 55%] [ 55%] tests/test_tutorial/test_custom_request_and_route/test_tutorial003.py .. [ 55%] [ 55%] tests/test_tutorial/test_custom_response/test_tutorial001.py . [ 55%] tests/test_tutorial/test_custom_response/test_tutorial001b.py . [ 55%] tests/test_tutorial/test_custom_response/test_tutorial004.py . [ 55%] tests/test_tutorial/test_custom_response/test_tutorial005.py .. [ 55%] tests/test_tutorial/test_custom_response/test_tutorial006.py .. [ 55%] tests/test_tutorial/test_custom_response/test_tutorial006b.py .. [ 55%] tests/test_tutorial/test_custom_response/test_tutorial006c.py .. [ 55%] tests/test_tutorial/test_custom_response/test_tutorial007.py . [ 55%] tests/test_tutorial/test_custom_response/test_tutorial008.py . [ 55%] tests/test_tutorial/test_custom_response/test_tutorial009.py . [ 55%] tests/test_tutorial/test_custom_response/test_tutorial009b.py . [ 55%] tests/test_tutorial/test_custom_response/test_tutorial009c.py . [ 56%] tests/test_tutorial/test_dataclasses/test_tutorial001.py ... [ 56%] tests/test_tutorial/test_dataclasses/test_tutorial002.py .. [ 56%] tests/test_tutorial/test_dataclasses/test_tutorial003.py ... [ 56%] tests/test_tutorial/test_dependencies/test_tutorial001.py ...... [ 56%] tests/test_tutorial/test_dependencies/test_tutorial001_an.py ...... [ 57%] tests/test_tutorial/test_dependencies/test_tutorial001_an_py310.py ..... [ 57%] . [ 57%] tests/test_tutorial/test_dependencies/test_tutorial001_an_py39.py ...... [ 57%] [ 57%] tests/test_tutorial/test_dependencies/test_tutorial001_py310.py ...... [ 58%] tests/test_tutorial/test_dependencies/test_tutorial004.py ....... [ 58%] tests/test_tutorial/test_dependencies/test_tutorial004_an.py ....... [ 58%] tests/test_tutorial/test_dependencies/test_tutorial004_an_py310.py ..... [ 59%] .. [ 59%] tests/test_tutorial/test_dependencies/test_tutorial004_an_py39.py ...... [ 59%] . [ 59%] tests/test_tutorial/test_dependencies/test_tutorial004_py310.py ....... [ 60%] tests/test_tutorial/test_dependencies/test_tutorial006.py ..... [ 60%] tests/test_tutorial/test_dependencies/test_tutorial006_an.py ..... [ 60%] tests/test_tutorial/test_dependencies/test_tutorial006_an_py39.py ..... [ 60%] tests/test_tutorial/test_dependencies/test_tutorial012.py ......... [ 61%] tests/test_tutorial/test_dependencies/test_tutorial012_an.py ......... [ 61%] tests/test_tutorial/test_dependencies/test_tutorial012_an_py39.py ...... [ 62%] ... [ 62%] tests/test_tutorial/test_events/test_tutorial001.py .. [ 62%] tests/test_tutorial/test_events/test_tutorial002.py .. [ 62%] tests/test_tutorial/test_events/test_tutorial003.py .. [ 62%] tests/test_tutorial/test_extending_openapi/test_tutorial001.py .. [ 62%] tests/test_tutorial/test_extending_openapi/test_tutorial002.py .... [ 63%] tests/test_tutorial/test_extending_openapi/test_tutorial003.py .. [ 63%] tests/test_tutorial/test_extending_openapi/test_tutorial004.py .. [ 63%] tests/test_tutorial/test_extending_openapi/test_tutorial005.py .. [ 63%] tests/test_tutorial/test_extra_data_types/test_tutorial001.py .. [ 63%] tests/test_tutorial/test_extra_data_types/test_tutorial001_an.py .. [ 63%] tests/test_tutorial/test_extra_data_types/test_tutorial001_an_py310.py . [ 63%] . [ 63%] tests/test_tutorial/test_extra_data_types/test_tutorial001_an_py39.py .. [ 63%] [ 63%] tests/test_tutorial/test_extra_data_types/test_tutorial001_py310.py .. [ 63%] tests/test_tutorial/test_extra_models/test_tutorial003.py ... [ 64%] tests/test_tutorial/test_extra_models/test_tutorial003_py310.py ... [ 64%] tests/test_tutorial/test_extra_models/test_tutorial004.py .. [ 64%] tests/test_tutorial/test_extra_models/test_tutorial004_py39.py .. [ 64%] tests/test_tutorial/test_extra_models/test_tutorial005.py .. [ 64%] tests/test_tutorial/test_extra_models/test_tutorial005_py39.py .. [ 64%] tests/test_tutorial/test_first_steps/test_tutorial001.py ... [ 64%] tests/test_tutorial/test_generate_clients/test_tutorial003.py .... [ 65%] tests/test_tutorial/test_handling_errors/test_tutorial001.py ... [ 65%] tests/test_tutorial/test_handling_errors/test_tutorial002.py ... [ 65%] tests/test_tutorial/test_handling_errors/test_tutorial003.py ... [ 65%] tests/test_tutorial/test_handling_errors/test_tutorial004.py .... [ 65%] tests/test_tutorial/test_handling_errors/test_tutorial005.py ... [ 66%] tests/test_tutorial/test_handling_errors/test_tutorial006.py .... [ 66%] tests/test_tutorial/test_metadata/test_tutorial001.py .. [ 66%] tests/test_tutorial/test_metadata/test_tutorial004.py .. [ 66%] tests/test_tutorial/test_openapi_callbacks/test_tutorial001.py ... [ 66%] tests/test_tutorial/test_path_operation_advanced_configurations/test_tutorial001.py . [ 66%] . [ 66%] tests/test_tutorial/test_path_operation_advanced_configurations/test_tutorial002.py . [ 66%] . [ 66%] tests/test_tutorial/test_path_operation_advanced_configurations/test_tutorial003.py . [ 66%] . [ 66%] tests/test_tutorial/test_path_operation_advanced_configurations/test_tutorial004.py . [ 67%] . [ 67%] tests/test_tutorial/test_path_operation_advanced_configurations/test_tutorial005.py . [ 67%] . [ 67%] tests/test_tutorial/test_path_operation_advanced_configurations/test_tutorial006.py . [ 67%] . [ 67%] tests/test_tutorial/test_path_operation_advanced_configurations/test_tutorial007.py . [ 67%] ... [ 67%] tests/test_tutorial/test_path_operation_configurations/test_tutorial002b.py . [ 67%] .. [ 67%] tests/test_tutorial/test_path_operation_configurations/test_tutorial005.py . [ 67%] . [ 67%] tests/test_tutorial/test_path_operation_configurations/test_tutorial005_py310.py . [ 67%] . [ 67%] tests/test_tutorial/test_path_operation_configurations/test_tutorial005_py39.py . [ 67%] . [ 68%] tests/test_tutorial/test_path_operation_configurations/test_tutorial006.py . [ 68%] ... [ 68%] tests/test_tutorial/test_path_params/test_tutorial004.py ... [ 68%] tests/test_tutorial/test_path_params/test_tutorial005.py ..... [ 68%] tests/test_tutorial/test_query_params/test_tutorial005.py .... [ 68%] tests/test_tutorial/test_query_params/test_tutorial006.py ... [ 69%] tests/test_tutorial/test_query_params/test_tutorial006_py310.py ... [ 69%] tests/test_tutorial/test_query_params_str_validations/test_tutorial010.py . [ 69%] .... [ 69%] tests/test_tutorial/test_query_params_str_validations/test_tutorial010_an.py . [ 69%] .... [ 69%] tests/test_tutorial/test_query_params_str_validations/test_tutorial010_an_py310.py . [ 69%] .... [ 70%] tests/test_tutorial/test_query_params_str_validations/test_tutorial010_an_py39.py . [ 70%] .... [ 70%] tests/test_tutorial/test_query_params_str_validations/test_tutorial010_py310.py . [ 70%] .... [ 70%] tests/test_tutorial/test_query_params_str_validations/test_tutorial011.py . [ 70%] .. [ 70%] tests/test_tutorial/test_query_params_str_validations/test_tutorial011_an.py . [ 70%] .. [ 70%] tests/test_tutorial/test_query_params_str_validations/test_tutorial011_an_py310.py . [ 71%] .. [ 71%] tests/test_tutorial/test_query_params_str_validations/test_tutorial011_an_py39.py . [ 71%] .. [ 71%] tests/test_tutorial/test_query_params_str_validations/test_tutorial011_py310.py . [ 71%] .. [ 71%] tests/test_tutorial/test_query_params_str_validations/test_tutorial011_py39.py . [ 71%] .. [ 71%] tests/test_tutorial/test_query_params_str_validations/test_tutorial012.py . [ 71%] .. [ 71%] tests/test_tutorial/test_query_params_str_validations/test_tutorial012_an.py . [ 71%] .. [ 71%] tests/test_tutorial/test_query_params_str_validations/test_tutorial012_an_py39.py . [ 72%] .. [ 72%] tests/test_tutorial/test_query_params_str_validations/test_tutorial012_py39.py . [ 72%] .. [ 72%] tests/test_tutorial/test_query_params_str_validations/test_tutorial013.py . [ 72%] .. [ 72%] tests/test_tutorial/test_query_params_str_validations/test_tutorial013_an.py . [ 72%] .. [ 72%] tests/test_tutorial/test_query_params_str_validations/test_tutorial013_an_py39.py . [ 72%] .. [ 72%] tests/test_tutorial/test_query_params_str_validations/test_tutorial014.py . [ 72%] .. [ 72%] tests/test_tutorial/test_query_params_str_validations/test_tutorial014_an.py . [ 73%] .. [ 73%] tests/test_tutorial/test_query_params_str_validations/test_tutorial014_an_py310.py . [ 73%] .. [ 73%] tests/test_tutorial/test_query_params_str_validations/test_tutorial014_an_py39.py . [ 73%] .. [ 73%] tests/test_tutorial/test_query_params_str_validations/test_tutorial014_py310.py . [ 73%] .. [ 73%] tests/test_tutorial/test_request_files/test_tutorial001.py ...... [ 73%] tests/test_tutorial/test_request_files/test_tutorial001_02.py ..... [ 74%] tests/test_tutorial/test_request_files/test_tutorial001_02_an.py ..... [ 74%] tests/test_tutorial/test_request_files/test_tutorial001_02_an_py310.py . [ 74%] .... [ 74%] tests/test_tutorial/test_request_files/test_tutorial001_02_an_py39.py .. [ 74%] ... [ 75%] tests/test_tutorial/test_request_files/test_tutorial001_02_py310.py .... [ 75%] . [ 75%] tests/test_tutorial/test_request_files/test_tutorial001_03.py ... [ 75%] tests/test_tutorial/test_request_files/test_tutorial001_03_an.py ... [ 75%] tests/test_tutorial/test_request_files/test_tutorial001_03_an_py39.py .. [ 75%] . [ 75%] tests/test_tutorial/test_request_files/test_tutorial001_an.py ...... [ 76%] tests/test_tutorial/test_request_files/test_tutorial001_an_py39.py ..... [ 76%] . [ 76%] tests/test_tutorial/test_request_files/test_tutorial002.py ...... [ 76%] tests/test_tutorial/test_request_files/test_tutorial002_an.py ...... [ 77%] tests/test_tutorial/test_request_files/test_tutorial002_an_py39.py ..... [ 77%] . [ 77%] tests/test_tutorial/test_request_files/test_tutorial002_py39.py ...... [ 77%] tests/test_tutorial/test_request_files/test_tutorial003.py .... [ 78%] tests/test_tutorial/test_request_files/test_tutorial003_an.py .... [ 78%] tests/test_tutorial/test_request_files/test_tutorial003_an_py39.py .... [ 78%] tests/test_tutorial/test_request_files/test_tutorial003_py39.py .... [ 78%] tests/test_tutorial/test_request_forms/test_tutorial001.py ...... [ 79%] tests/test_tutorial/test_request_forms/test_tutorial001_an.py ...... [ 79%] tests/test_tutorial/test_request_forms/test_tutorial001_an_py39.py ..... [ 79%] . [ 79%] tests/test_tutorial/test_request_forms_and_files/test_tutorial001.py ... [ 79%] ... [ 80%] tests/test_tutorial/test_request_forms_and_files/test_tutorial001_an.py . [ 80%] ..... [ 80%] tests/test_tutorial/test_request_forms_and_files/test_tutorial001_an_py39.py . [ 80%] ..... [ 80%] tests/test_tutorial/test_response_change_status_code/test_tutorial001.py . [ 80%] [ 80%] tests/test_tutorial/test_response_cookies/test_tutorial001.py . [ 80%] tests/test_tutorial/test_response_cookies/test_tutorial002.py . [ 80%] tests/test_tutorial/test_response_headers/test_tutorial001.py . [ 80%] tests/test_tutorial/test_response_headers/test_tutorial002.py . [ 81%] tests/test_tutorial/test_response_model/test_tutorial003.py .. [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_01.py .. [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_01_py310.py .. [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_02.py ... [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_03.py .. [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_04.py . [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_04_py310.py . [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_05.py ... [ 81%] tests/test_tutorial/test_response_model/test_tutorial003_05_py310.py ... [ 82%] [ 82%] tests/test_tutorial/test_response_model/test_tutorial003_py310.py .. [ 82%] tests/test_tutorial/test_response_model/test_tutorial004.py .... [ 82%] tests/test_tutorial/test_response_model/test_tutorial004_py310.py .... [ 82%] tests/test_tutorial/test_response_model/test_tutorial004_py39.py .... [ 82%] tests/test_tutorial/test_response_model/test_tutorial005.py ... [ 83%] tests/test_tutorial/test_response_model/test_tutorial005_py310.py ... [ 83%] tests/test_tutorial/test_response_model/test_tutorial006.py ... [ 83%] tests/test_tutorial/test_response_model/test_tutorial006_py310.py ... [ 83%] tests/test_tutorial/test_schema_extra_example/test_tutorial004.py .. [ 83%] tests/test_tutorial/test_schema_extra_example/test_tutorial004_an.py .. [ 83%] tests/test_tutorial/test_schema_extra_example/test_tutorial004_an_py310.py . [ 83%] . [ 83%] tests/test_tutorial/test_schema_extra_example/test_tutorial004_an_py39.py . [ 83%] . [ 83%] tests/test_tutorial/test_schema_extra_example/test_tutorial004_py310.py . [ 84%] . [ 84%] tests/test_tutorial/test_security/test_tutorial001.py .... [ 84%] tests/test_tutorial/test_security/test_tutorial001_an.py .... [ 84%] tests/test_tutorial/test_security/test_tutorial001_an_py39.py .... [ 84%] tests/test_tutorial/test_security/test_tutorial003.py ......... [ 85%] tests/test_tutorial/test_security/test_tutorial003_an.py ......... [ 85%] tests/test_tutorial/test_security/test_tutorial003_an_py310.py ......... [ 86%] [ 86%] tests/test_tutorial/test_security/test_tutorial003_an_py39.py ......... [ 86%] tests/test_tutorial/test_security/test_tutorial003_py310.py ......... [ 87%] tests/test_tutorial/test_security/test_tutorial005.py .................. [ 88%] . [ 88%] tests/test_tutorial/test_security/test_tutorial005_an.py ............... [ 89%] .... [ 89%] tests/test_tutorial/test_security/test_tutorial005_an_py310.py ......... [ 89%] .......... [ 90%] tests/test_tutorial/test_security/test_tutorial005_an_py39.py .......... [ 90%] ......... [ 91%] tests/test_tutorial/test_security/test_tutorial005_py310.py ............ [ 92%] ....... [ 92%] tests/test_tutorial/test_security/test_tutorial005_py39.py ............. [ 93%] ...... [ 93%] tests/test_tutorial/test_security/test_tutorial006.py ..... [ 93%] tests/test_tutorial/test_security/test_tutorial006_an.py ..... [ 94%] tests/test_tutorial/test_security/test_tutorial006_an_py39.py ..... [ 94%] tests/test_tutorial/test_settings/test_app02.py .. [ 94%] tests/test_tutorial/test_sql_databases_peewee/test_sql_databases_peewee.py . [ 94%] ....... [ 94%] tests/test_tutorial/test_sub_applications/test_tutorial001.py .... [ 95%] tests/test_tutorial/test_templates/test_tutorial001.py . [ 95%] tests/test_tutorial/test_testing/test_main.py ... [ 95%] tests/test_tutorial/test_testing/test_main_b.py . [ 95%] tests/test_tutorial/test_testing/test_main_b_an.py . [ 95%] tests/test_tutorial/test_testing/test_main_b_an_py310.py . [ 95%] tests/test_tutorial/test_testing/test_main_b_an_py39.py . [ 95%] tests/test_tutorial/test_testing/test_main_b_py310.py . [ 95%] tests/test_tutorial/test_testing/test_tutorial001.py ... [ 95%] tests/test_tutorial/test_testing/test_tutorial002.py .... [ 96%] tests/test_tutorial/test_testing/test_tutorial003.py .. [ 96%] tests/test_tutorial/test_testing_dependencies/test_tutorial001.py ...... [ 96%] .... [ 96%] tests/test_tutorial/test_testing_dependencies/test_tutorial001_an.py ... [ 96%] ....... [ 97%] tests/test_tutorial/test_testing_dependencies/test_tutorial001_an_py310.py . [ 97%] ...... [ 97%] tests/test_tutorial/test_testing_dependencies/test_tutorial001_an_py39.py . [ 97%] ...... [ 98%] tests/test_tutorial/test_testing_dependencies/test_tutorial001_py310.py . [ 98%] ...... [ 98%] tests/test_tutorial/test_websockets/test_tutorial001.py .. [ 98%] tests/test_tutorial/test_websockets/test_tutorial002.py .... [ 98%] tests/test_tutorial/test_websockets/test_tutorial002_an.py .... [ 99%] tests/test_tutorial/test_websockets/test_tutorial002_an_py310.py .... [ 99%] tests/test_tutorial/test_websockets/test_tutorial002_an_py39.py .... [ 99%] tests/test_tutorial/test_websockets/test_tutorial002_py310.py .... [ 99%] tests/test_tutorial/test_websockets/test_tutorial003.py .. [ 99%] tests/test_tutorial/test_websockets/test_tutorial003_py39.py .. [ 99%] tests/test_tutorial/test_wsgi/test_tutorial001.py .. [100%] ===================== 1801 passed, 78 deselected in 33.38s ===================== Finished executing pytestCheckPhase pytestCheckPhase completed in 34 seconds pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/99abrnjggcyc6fqqqbmz4fndf3fnxkyf-python3.10-mocket-3.11.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/bxysyq3akwyh9g3xjmgpgc22dg8aqldn-mocket-3.11.0.tar.gz source root is mocket-3.11.0 setting SOURCE_DATE_EPOCH to timestamp 1676822196 of file mocket-3.11.0/setup.cfg patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/mocket copying mocket/utils.py -> build/lib/mocket copying mocket/__init__.py -> build/lib/mocket copying mocket/async_mocket.py -> build/lib/mocket copying mocket/compat.py -> build/lib/mocket copying mocket/exceptions.py -> build/lib/mocket copying mocket/mockredis.py -> build/lib/mocket copying mocket/mockhttp.py -> build/lib/mocket copying mocket/mocket.py -> build/lib/mocket creating build/lib/mocket/plugins copying mocket/plugins/__init__.py -> build/lib/mocket/plugins copying mocket/plugins/pook_mock_engine.py -> build/lib/mocket/plugins creating build/lib/mocket/plugins/httpretty copying mocket/plugins/httpretty/core.py -> build/lib/mocket/plugins/httpretty copying mocket/plugins/httpretty/__init__.py -> build/lib/mocket/plugins/httpretty /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/mocket copying build/lib/mocket/compat.py -> build/bdist.linux-x86_64/wheel/mocket copying build/lib/mocket/mockhttp.py -> build/bdist.linux-x86_64/wheel/mocket copying build/lib/mocket/mockredis.py -> build/bdist.linux-x86_64/wheel/mocket copying build/lib/mocket/exceptions.py -> build/bdist.linux-x86_64/wheel/mocket copying build/lib/mocket/utils.py -> build/bdist.linux-x86_64/wheel/mocket creating build/bdist.linux-x86_64/wheel/mocket/plugins copying build/lib/mocket/plugins/__init__.py -> build/bdist.linux-x86_64/wheel/mocket/plugins creating build/bdist.linux-x86_64/wheel/mocket/plugins/httpretty copying build/lib/mocket/plugins/httpretty/core.py -> build/bdist.linux-x86_64/wheel/mocket/plugins/httpretty copying build/lib/mocket/plugins/httpretty/__init__.py -> build/bdist.linux-x86_64/wheel/mocket/plugins/httpretty copying build/lib/mocket/plugins/pook_mock_engine.py -> build/bdist.linux-x86_64/wheel/mocket/plugins copying build/lib/mocket/async_mocket.py -> build/bdist.linux-x86_64/wheel/mocket copying build/lib/mocket/mocket.py -> build/bdist.linux-x86_64/wheel/mocket copying build/lib/mocket/__init__.py -> build/bdist.linux-x86_64/wheel/mocket running install_egg_info running egg_info writing mocket.egg-info/PKG-INFO writing dependency_links to mocket.egg-info/dependency_links.txt writing requirements to mocket.egg-info/requires.txt writing top-level names to mocket.egg-info/top_level.txt reading manifest file 'mocket.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'mocket.egg-info/SOURCES.txt' Copying mocket.egg-info to build/bdist.linux-x86_64/wheel/mocket-3.11.0-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/mocket-3.11.0.dist-info/WHEEL creating 'dist/mocket-3.11.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'mocket/__init__.py' adding 'mocket/async_mocket.py' adding 'mocket/compat.py' adding 'mocket/exceptions.py' adding 'mocket/mocket.py' adding 'mocket/mockhttp.py' adding 'mocket/mockredis.py' adding 'mocket/utils.py' adding 'mocket/plugins/__init__.py' adding 'mocket/plugins/pook_mock_engine.py' adding 'mocket/plugins/httpretty/__init__.py' adding 'mocket/plugins/httpretty/core.py' adding 'mocket-3.11.0.dist-info/LICENSE' adding 'mocket-3.11.0.dist-info/METADATA' adding 'mocket-3.11.0.dist-info/WHEEL' adding 'mocket-3.11.0.dist-info/top_level.txt' adding 'mocket-3.11.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed mocket-3.11.0-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/4am99snf70dh7hl37cqyjh0gmbz0khki-python3.10-mocket-3.11.0 checking for references to /build/ in /nix/store/4am99snf70dh7hl37cqyjh0gmbz0khki-python3.10-mocket-3.11.0... patching script interpreter paths in /nix/store/4am99snf70dh7hl37cqyjh0gmbz0khki-python3.10-mocket-3.11.0 stripping (with command strip and flags -S -p) in /nix/store/4am99snf70dh7hl37cqyjh0gmbz0khki-python3.10-mocket-3.11.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/z1vqsj93h3pk15w63pgjfqi40b7jj95a-python3.10-mocket-3.11.0-dist checking for references to /build/ in /nix/store/z1vqsj93h3pk15w63pgjfqi40b7jj95a-python3.10-mocket-3.11.0-dist... patching script interpreter paths in /nix/store/z1vqsj93h3pk15w63pgjfqi40b7jj95a-python3.10-mocket-3.11.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: mocket pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/mocket-3.11.0 plugins: anyio-3.7.1, devtools-0.11.0, mock-3.11.1 collected 119 items / 14 deselected / 105 selected tests/main/test_http.py .................. [ 17%] tests/main/test_http_aiohttp.py .XX [ 20%] tests/main/test_http_gevent.py .................................... [ 54%] tests/main/test_httpretty.py ................ [ 69%] tests/main/test_https.py . [ 70%] tests/main/test_mocket.py ..................... [ 90%] tests/main/test_mode.py .s [ 92%] tests/main/test_pook.py . [ 93%] tests/tests37/test_httpx.py ss. [ 96%] tests/tests38/test_http_aiohttp.py ..X. [100%] =============================== warnings summary =============================== ../../nix/store/4pb1igl23lpqwsjvccssvcs2ngmfz2j2-python3.10-gevent-22.10.2/lib/python3.10/site-packages/gevent/events.py:74 /nix/store/4pb1igl23lpqwsjvccssvcs2ngmfz2j2-python3.10-gevent-22.10.2/lib/python3.10/site-packages/gevent/events.py:74: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html from pkg_resources import iter_entry_points ../../nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/pkg_resources/__init__.py:2871 ../../nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/pkg_resources/__init__.py:2871 /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/pkg_resources/__init__.py:2871: DeprecationWarning: Deprecated call to `pkg_resources.declare_namespace('zope')`. Implementing implicit namespace packages (as specified in PEP 420) is preferred to `pkg_resources.declare_namespace`. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages declare_namespace(pkg) tests/tests37/test_httpx.py:12 /build/mocket-3.11.0/tests/tests37/test_httpx.py:12: PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html @pytest.mark.asyncio tests/tests37/test_httpx.py:37 /build/mocket-3.11.0/tests/tests37/test_httpx.py:37: PytestUnknownMarkWarning: Unknown pytest.mark.asyncio - is this a typo? You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html @pytest.mark.asyncio tests/tests37/test_httpx.py::test_httpx_decorator tests/tests37/test_httpx.py::test_httpx_fixture /nix/store/s3rq2p38bq0pcyqfmikhdjc7crl5411z-python3.10-pytest-7.4.0/lib/python3.10/site-packages/_pytest/python.py:183: PytestUnhandledCoroutineWarning: async def functions are not natively supported and have been skipped. You need to install a suitable plugin for your async framework, for example: - anyio - pytest-asyncio - pytest-tornasync - pytest-trio - pytest-twisted warnings.warn(PytestUnhandledCoroutineWarning(msg.format(nodeid))) -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ===== 99 passed, 3 skipped, 14 deselected, 3 xpassed, 7 warnings in 0.84s ====== Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/6n00xfrq85znawka0ab0vzqd62dpgj7z-python3.10-geoip2-4.7.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/8q5gqqkqp3i1fw5rkqn9iqrgv4bbnp99-geoip2-4.7.0.tar.gz source root is geoip2-4.7.0 setting SOURCE_DATE_EPOCH to timestamp 1683663998 of file geoip2-4.7.0/setup.cfg patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel The [wheel] section is deprecated. Use [bdist_wheel] instead. running build running build_py creating build creating build/lib creating build/lib/geoip2 copying geoip2/errors.py -> build/lib/geoip2 copying geoip2/__init__.py -> build/lib/geoip2 copying geoip2/database.py -> build/lib/geoip2 copying geoip2/webservice.py -> build/lib/geoip2 copying geoip2/types.py -> build/lib/geoip2 copying geoip2/records.py -> build/lib/geoip2 copying geoip2/models.py -> build/lib/geoip2 copying geoip2/mixins.py -> build/lib/geoip2 running egg_info writing geoip2.egg-info/PKG-INFO writing dependency_links to geoip2.egg-info/dependency_links.txt writing requirements to geoip2.egg-info/requires.txt writing top-level names to geoip2.egg-info/top_level.txt reading manifest file 'geoip2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'geoip2.egg-info/SOURCES.txt' copying geoip2/py.typed -> build/lib/geoip2 /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/records.py -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/py.typed -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/models.py -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/mixins.py -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/types.py -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/database.py -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/errors.py -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/webservice.py -> build/bdist.linux-x86_64/wheel/geoip2 copying build/lib/geoip2/__init__.py -> build/bdist.linux-x86_64/wheel/geoip2 running install_egg_info Copying geoip2.egg-info to build/bdist.linux-x86_64/wheel/geoip2-4.7.0-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/geoip2-4.7.0.dist-info/WHEEL creating 'dist/geoip2-4.7.0-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'geoip2/__init__.py' adding 'geoip2/database.py' adding 'geoip2/errors.py' adding 'geoip2/mixins.py' adding 'geoip2/models.py' adding 'geoip2/py.typed' adding 'geoip2/records.py' adding 'geoip2/types.py' adding 'geoip2/webservice.py' adding 'geoip2-4.7.0.dist-info/LICENSE' adding 'geoip2-4.7.0.dist-info/METADATA' adding 'geoip2-4.7.0.dist-info/WHEEL' adding 'geoip2-4.7.0.dist-info/top_level.txt' adding 'geoip2-4.7.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed geoip2-4.7.0-py2.py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/acyh6lan1vb6f6vhjiwp62vlyyvpdjmk-python3.10-geoip2-4.7.0 checking for references to /build/ in /nix/store/acyh6lan1vb6f6vhjiwp62vlyyvpdjmk-python3.10-geoip2-4.7.0... patching script interpreter paths in /nix/store/acyh6lan1vb6f6vhjiwp62vlyyvpdjmk-python3.10-geoip2-4.7.0 stripping (with command strip and flags -S -p) in /nix/store/acyh6lan1vb6f6vhjiwp62vlyyvpdjmk-python3.10-geoip2-4.7.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/j4mwlj3is68nm034rqrx9kmqiv5b13ad-python3.10-geoip2-4.7.0-dist checking for references to /build/ in /nix/store/j4mwlj3is68nm034rqrx9kmqiv5b13ad-python3.10-geoip2-4.7.0-dist... patching script interpreter paths in /nix/store/j4mwlj3is68nm034rqrx9kmqiv5b13ad-python3.10-geoip2-4.7.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: geoip2 pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/geoip2-4.7.0 plugins: requests-mock-1.11.0 collected 151 items / 2 deselected / 149 selected tests/database_test.py ................................................. [ 32%] ......................................... [ 60%] tests/models_test.py ......... [ 66%] tests/webservice_test.py ............................................... [ 97%] ... [100%] ====================== 149 passed, 2 deselected in 0.33s ======================= Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/r4nqpn2nvz9h0jwrzndjrz5vsb55ijy2-python3.10-Django-4.2.5.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh unpacking sources unpacking source archive /nix/store/if7dyfi2dfbgkrnsswk2k6x9mj0jyr8d-Django-4.2.5.tar.gz source root is Django-4.2.5 setting SOURCE_DATE_EPOCH to timestamp 1693822053 of file Django-4.2.5/setup.cfg patching sources applying patch /nix/store/dvkim3dsj3llkha66zwx8m553jbrf315-django_4_set_zoneinfo_dir.patch patching file django/conf/__init__.py Hunk #1 succeeded at 254 (offset 27 lines). applying patch /nix/store/2q50q9ldqshmdd4yjiwf9zfzzf57qf57-django_4_tests.patch patching file tests/admin_scripts/tests.py patching file tests/auth_tests/test_hashers.py patching file tests/settings_tests/tests.py updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing pypaBuildPhase Creating a wheel... * Getting build dependencies for wheel... running egg_info writing Django.egg-info/PKG-INFO writing dependency_links to Django.egg-info/dependency_links.txt writing entry points to Django.egg-info/entry_points.txt writing requirements to Django.egg-info/requires.txt writing top-level names to Django.egg-info/top_level.txt reading manifest file 'Django.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found anywhere in distribution adding license file 'LICENSE' adding license file 'LICENSE.python' adding license file 'AUTHORS' writing manifest file 'Django.egg-info/SOURCES.txt' * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/django copying django/__main__.py -> build/lib/django copying django/shortcuts.py -> build/lib/django copying django/__init__.py -> build/lib/django creating build/lib/django/utils copying django/utils/functional.py -> build/lib/django/utils copying django/utils/dateparse.py -> build/lib/django/utils copying django/utils/connection.py -> build/lib/django/utils copying django/utils/version.py -> build/lib/django/utils copying django/utils/xmlutils.py -> build/lib/django/utils copying django/utils/deprecation.py -> build/lib/django/utils copying django/utils/timesince.py -> build/lib/django/utils copying django/utils/itercompat.py -> build/lib/django/utils copying django/utils/tree.py -> build/lib/django/utils copying django/utils/feedgenerator.py -> build/lib/django/utils copying django/utils/dates.py -> build/lib/django/utils copying django/utils/inspect.py -> build/lib/django/utils copying django/utils/regex_helper.py -> build/lib/django/utils copying django/utils/autoreload.py -> build/lib/django/utils copying django/utils/baseconv.py -> build/lib/django/utils copying django/utils/datetime_safe.py -> build/lib/django/utils copying django/utils/__init__.py -> build/lib/django/utils copying django/utils/timezone.py -> build/lib/django/utils copying django/utils/safestring.py -> build/lib/django/utils copying django/utils/module_loading.py -> build/lib/django/utils copying django/utils/encoding.py -> build/lib/django/utils copying django/utils/_os.py -> build/lib/django/utils copying django/utils/crypto.py -> build/lib/django/utils copying django/utils/duration.py -> build/lib/django/utils copying django/utils/archive.py -> build/lib/django/utils copying django/utils/topological_sort.py -> build/lib/django/utils copying django/utils/decorators.py -> build/lib/django/utils copying django/utils/formats.py -> build/lib/django/utils copying django/utils/http.py -> build/lib/django/utils copying django/utils/termcolors.py -> build/lib/django/utils copying django/utils/datastructures.py -> build/lib/django/utils copying django/utils/text.py -> build/lib/django/utils copying django/utils/ipv6.py -> build/lib/django/utils copying django/utils/lorem_ipsum.py -> build/lib/django/utils copying django/utils/asyncio.py -> build/lib/django/utils copying django/utils/jslex.py -> build/lib/django/utils copying django/utils/html.py -> build/lib/django/utils copying django/utils/numberformat.py -> build/lib/django/utils copying django/utils/log.py -> build/lib/django/utils copying django/utils/hashable.py -> build/lib/django/utils copying django/utils/deconstruct.py -> build/lib/django/utils copying django/utils/dateformat.py -> build/lib/django/utils copying django/utils/cache.py -> build/lib/django/utils creating build/lib/django/apps copying django/apps/__init__.py -> build/lib/django/apps copying django/apps/registry.py -> build/lib/django/apps copying django/apps/config.py -> build/lib/django/apps creating build/lib/django/views copying django/views/csrf.py -> build/lib/django/views copying django/views/debug.py -> build/lib/django/views copying django/views/defaults.py -> build/lib/django/views copying django/views/__init__.py -> build/lib/django/views copying django/views/static.py -> build/lib/django/views copying django/views/i18n.py -> build/lib/django/views creating build/lib/django/core copying django/core/exceptions.py -> build/lib/django/core copying django/core/paginator.py -> build/lib/django/core copying django/core/signing.py -> build/lib/django/core copying django/core/__init__.py -> build/lib/django/core copying django/core/asgi.py -> build/lib/django/core copying django/core/validators.py -> build/lib/django/core copying django/core/signals.py -> build/lib/django/core copying django/core/wsgi.py -> build/lib/django/core creating build/lib/django/forms copying django/forms/renderers.py -> build/lib/django/forms copying django/forms/fields.py -> build/lib/django/forms copying django/forms/widgets.py -> build/lib/django/forms copying django/forms/forms.py -> build/lib/django/forms copying django/forms/__init__.py -> build/lib/django/forms copying django/forms/utils.py -> build/lib/django/forms copying django/forms/boundfield.py -> build/lib/django/forms copying django/forms/formsets.py -> build/lib/django/forms copying django/forms/models.py -> build/lib/django/forms creating build/lib/django/template copying django/template/loader_tags.py -> build/lib/django/template copying django/template/autoreload.py -> build/lib/django/template copying django/template/base.py -> build/lib/django/template copying django/template/context_processors.py -> build/lib/django/template copying django/template/context.py -> build/lib/django/template copying django/template/defaultfilters.py -> build/lib/django/template copying django/template/loader.py -> build/lib/django/template copying django/template/response.py -> build/lib/django/template copying django/template/smartif.py -> build/lib/django/template copying django/template/__init__.py -> build/lib/django/template copying django/template/library.py -> build/lib/django/template copying django/template/defaulttags.py -> build/lib/django/template copying django/template/engine.py -> build/lib/django/template copying django/template/utils.py -> build/lib/django/template copying django/template/exceptions.py -> build/lib/django/template creating build/lib/django/templatetags copying django/templatetags/l10n.py -> build/lib/django/templatetags copying django/templatetags/i18n.py -> build/lib/django/templatetags copying django/templatetags/tz.py -> build/lib/django/templatetags copying django/templatetags/static.py -> build/lib/django/templatetags copying django/templatetags/cache.py -> build/lib/django/templatetags copying django/templatetags/__init__.py -> build/lib/django/templatetags creating build/lib/django/db copying django/db/utils.py -> build/lib/django/db copying django/db/__init__.py -> build/lib/django/db copying django/db/transaction.py -> build/lib/django/db creating build/lib/django/urls copying django/urls/__init__.py -> build/lib/django/urls copying django/urls/converters.py -> build/lib/django/urls copying django/urls/conf.py -> build/lib/django/urls copying django/urls/exceptions.py -> build/lib/django/urls copying django/urls/resolvers.py -> build/lib/django/urls copying django/urls/base.py -> build/lib/django/urls copying django/urls/utils.py -> build/lib/django/urls creating build/lib/django/http copying django/http/__init__.py -> build/lib/django/http copying django/http/cookie.py -> build/lib/django/http copying django/http/response.py -> build/lib/django/http copying django/http/multipartparser.py -> build/lib/django/http copying django/http/request.py -> build/lib/django/http creating build/lib/django/test copying django/test/client.py -> build/lib/django/test copying django/test/runner.py -> build/lib/django/test copying django/test/selenium.py -> build/lib/django/test copying django/test/utils.py -> build/lib/django/test copying django/test/html.py -> build/lib/django/test copying django/test/__init__.py -> build/lib/django/test copying django/test/testcases.py -> build/lib/django/test copying django/test/signals.py -> build/lib/django/test creating build/lib/django/contrib copying django/contrib/__init__.py -> build/lib/django/contrib creating build/lib/django/conf copying django/conf/__init__.py -> build/lib/django/conf copying django/conf/global_settings.py -> build/lib/django/conf creating build/lib/django/dispatch copying django/dispatch/__init__.py -> build/lib/django/dispatch copying django/dispatch/dispatcher.py -> build/lib/django/dispatch creating build/lib/django/middleware copying django/middleware/cache.py -> build/lib/django/middleware copying django/middleware/locale.py -> build/lib/django/middleware copying django/middleware/http.py -> build/lib/django/middleware copying django/middleware/csrf.py -> build/lib/django/middleware copying django/middleware/security.py -> build/lib/django/middleware copying django/middleware/common.py -> build/lib/django/middleware copying django/middleware/gzip.py -> build/lib/django/middleware copying django/middleware/__init__.py -> build/lib/django/middleware copying django/middleware/clickjacking.py -> build/lib/django/middleware creating build/lib/django/utils/translation copying django/utils/translation/__init__.py -> build/lib/django/utils/translation copying django/utils/translation/template.py -> build/lib/django/utils/translation copying django/utils/translation/trans_real.py -> build/lib/django/utils/translation copying django/utils/translation/reloader.py -> build/lib/django/utils/translation copying django/utils/translation/trans_null.py -> build/lib/django/utils/translation creating build/lib/django/views/generic copying django/views/generic/__init__.py -> build/lib/django/views/generic copying django/views/generic/edit.py -> build/lib/django/views/generic copying django/views/generic/list.py -> build/lib/django/views/generic copying django/views/generic/base.py -> build/lib/django/views/generic copying django/views/generic/detail.py -> build/lib/django/views/generic copying django/views/generic/dates.py -> build/lib/django/views/generic creating build/lib/django/views/decorators copying django/views/decorators/gzip.py -> build/lib/django/views/decorators copying django/views/decorators/common.py -> build/lib/django/views/decorators copying django/views/decorators/cache.py -> build/lib/django/views/decorators copying django/views/decorators/csrf.py -> build/lib/django/views/decorators copying django/views/decorators/http.py -> build/lib/django/views/decorators copying django/views/decorators/debug.py -> build/lib/django/views/decorators copying django/views/decorators/vary.py -> build/lib/django/views/decorators copying django/views/decorators/__init__.py -> build/lib/django/views/decorators copying django/views/decorators/clickjacking.py -> build/lib/django/views/decorators creating build/lib/django/core/serializers copying django/core/serializers/json.py -> build/lib/django/core/serializers copying django/core/serializers/jsonl.py -> build/lib/django/core/serializers copying django/core/serializers/pyyaml.py -> build/lib/django/core/serializers copying django/core/serializers/base.py -> build/lib/django/core/serializers copying django/core/serializers/python.py -> build/lib/django/core/serializers copying django/core/serializers/__init__.py -> build/lib/django/core/serializers copying django/core/serializers/xml_serializer.py -> build/lib/django/core/serializers creating build/lib/django/core/checks copying django/core/checks/model_checks.py -> build/lib/django/core/checks copying django/core/checks/messages.py -> build/lib/django/core/checks copying django/core/checks/translation.py -> build/lib/django/core/checks copying django/core/checks/files.py -> build/lib/django/core/checks copying django/core/checks/caches.py -> build/lib/django/core/checks copying django/core/checks/urls.py -> build/lib/django/core/checks copying django/core/checks/async_checks.py -> build/lib/django/core/checks copying django/core/checks/registry.py -> build/lib/django/core/checks copying django/core/checks/database.py -> build/lib/django/core/checks copying django/core/checks/templates.py -> build/lib/django/core/checks copying django/core/checks/__init__.py -> build/lib/django/core/checks creating build/lib/django/core/files copying django/core/files/images.py -> build/lib/django/core/files copying django/core/files/uploadedfile.py -> build/lib/django/core/files copying django/core/files/temp.py -> build/lib/django/core/files copying django/core/files/utils.py -> build/lib/django/core/files copying django/core/files/uploadhandler.py -> build/lib/django/core/files copying django/core/files/locks.py -> build/lib/django/core/files copying django/core/files/base.py -> build/lib/django/core/files copying django/core/files/__init__.py -> build/lib/django/core/files copying django/core/files/move.py -> build/lib/django/core/files creating build/lib/django/core/handlers copying django/core/handlers/__init__.py -> build/lib/django/core/handlers copying django/core/handlers/wsgi.py -> build/lib/django/core/handlers copying django/core/handlers/exception.py -> build/lib/django/core/handlers copying django/core/handlers/base.py -> build/lib/django/core/handlers copying django/core/handlers/asgi.py -> build/lib/django/core/handlers creating build/lib/django/core/mail copying django/core/mail/message.py -> build/lib/django/core/mail copying django/core/mail/utils.py -> build/lib/django/core/mail copying django/core/mail/__init__.py -> build/lib/django/core/mail creating build/lib/django/core/cache copying django/core/cache/utils.py -> build/lib/django/core/cache copying django/core/cache/__init__.py -> build/lib/django/core/cache creating build/lib/django/core/servers copying django/core/servers/__init__.py -> build/lib/django/core/servers copying django/core/servers/basehttp.py -> build/lib/django/core/servers creating build/lib/django/core/management copying django/core/management/color.py -> build/lib/django/core/management copying django/core/management/utils.py -> build/lib/django/core/management copying django/core/management/base.py -> build/lib/django/core/management copying django/core/management/__init__.py -> build/lib/django/core/management copying django/core/management/templates.py -> build/lib/django/core/management copying django/core/management/sql.py -> build/lib/django/core/management creating build/lib/django/core/checks/compatibility copying django/core/checks/compatibility/__init__.py -> build/lib/django/core/checks/compatibility copying django/core/checks/compatibility/django_4_0.py -> build/lib/django/core/checks/compatibility creating build/lib/django/core/checks/security copying django/core/checks/security/base.py -> build/lib/django/core/checks/security copying django/core/checks/security/sessions.py -> build/lib/django/core/checks/security copying django/core/checks/security/__init__.py -> build/lib/django/core/checks/security copying django/core/checks/security/csrf.py -> build/lib/django/core/checks/security creating build/lib/django/core/files/storage copying django/core/files/storage/__init__.py -> build/lib/django/core/files/storage copying django/core/files/storage/base.py -> build/lib/django/core/files/storage copying django/core/files/storage/filesystem.py -> build/lib/django/core/files/storage copying django/core/files/storage/handler.py -> build/lib/django/core/files/storage copying django/core/files/storage/memory.py -> build/lib/django/core/files/storage copying django/core/files/storage/mixins.py -> build/lib/django/core/files/storage creating build/lib/django/core/mail/backends copying django/core/mail/backends/dummy.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/base.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/__init__.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/console.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/filebased.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/smtp.py -> build/lib/django/core/mail/backends copying django/core/mail/backends/locmem.py -> build/lib/django/core/mail/backends creating build/lib/django/core/cache/backends copying django/core/cache/backends/locmem.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/filebased.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/redis.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/__init__.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/dummy.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/base.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/memcached.py -> build/lib/django/core/cache/backends copying django/core/cache/backends/db.py -> build/lib/django/core/cache/backends creating build/lib/django/core/management/commands copying django/core/management/commands/compilemessages.py -> build/lib/django/core/management/commands copying django/core/management/commands/sqlflush.py -> build/lib/django/core/management/commands copying django/core/management/commands/startapp.py -> build/lib/django/core/management/commands copying django/core/management/commands/check.py -> build/lib/django/core/management/commands copying django/core/management/commands/squashmigrations.py -> build/lib/django/core/management/commands copying django/core/management/commands/testserver.py -> build/lib/django/core/management/commands copying django/core/management/commands/sendtestemail.py -> build/lib/django/core/management/commands copying django/core/management/commands/makemessages.py -> build/lib/django/core/management/commands copying django/core/management/commands/runserver.py -> build/lib/django/core/management/commands copying django/core/management/commands/inspectdb.py -> build/lib/django/core/management/commands copying django/core/management/commands/sqlsequencereset.py -> build/lib/django/core/management/commands copying django/core/management/commands/createcachetable.py -> build/lib/django/core/management/commands copying django/core/management/commands/makemigrations.py -> build/lib/django/core/management/commands copying django/core/management/commands/loaddata.py -> build/lib/django/core/management/commands copying django/core/management/commands/dbshell.py -> build/lib/django/core/management/commands copying django/core/management/commands/shell.py -> build/lib/django/core/management/commands copying django/core/management/commands/startproject.py -> build/lib/django/core/management/commands copying django/core/management/commands/test.py -> build/lib/django/core/management/commands copying django/core/management/commands/migrate.py -> build/lib/django/core/management/commands copying django/core/management/commands/sqlmigrate.py -> build/lib/django/core/management/commands copying django/core/management/commands/flush.py -> build/lib/django/core/management/commands copying django/core/management/commands/optimizemigration.py -> build/lib/django/core/management/commands copying django/core/management/commands/dumpdata.py -> build/lib/django/core/management/commands copying django/core/management/commands/__init__.py -> build/lib/django/core/management/commands copying django/core/management/commands/diffsettings.py -> build/lib/django/core/management/commands copying django/core/management/commands/showmigrations.py -> build/lib/django/core/management/commands creating build/lib/django/template/loaders copying django/template/loaders/base.py -> build/lib/django/template/loaders copying django/template/loaders/locmem.py -> build/lib/django/template/loaders copying django/template/loaders/__init__.py -> build/lib/django/template/loaders copying django/template/loaders/filesystem.py -> build/lib/django/template/loaders copying django/template/loaders/cached.py -> build/lib/django/template/loaders copying django/template/loaders/app_directories.py -> build/lib/django/template/loaders creating build/lib/django/template/backends copying django/template/backends/base.py -> build/lib/django/template/backends copying django/template/backends/dummy.py -> build/lib/django/template/backends copying django/template/backends/django.py -> build/lib/django/template/backends copying django/template/backends/jinja2.py -> build/lib/django/template/backends copying django/template/backends/utils.py -> build/lib/django/template/backends copying django/template/backends/__init__.py -> build/lib/django/template/backends creating build/lib/django/db/backends copying django/db/backends/utils.py -> build/lib/django/db/backends copying django/db/backends/signals.py -> build/lib/django/db/backends copying django/db/backends/__init__.py -> build/lib/django/db/backends copying django/db/backends/ddl_references.py -> build/lib/django/db/backends creating build/lib/django/db/models copying django/db/models/constants.py -> build/lib/django/db/models copying django/db/models/query_utils.py -> build/lib/django/db/models copying django/db/models/base.py -> build/lib/django/db/models copying django/db/models/manager.py -> build/lib/django/db/models copying django/db/models/expressions.py -> build/lib/django/db/models copying django/db/models/lookups.py -> build/lib/django/db/models copying django/db/models/constraints.py -> build/lib/django/db/models copying django/db/models/enums.py -> build/lib/django/db/models copying django/db/models/query.py -> build/lib/django/db/models copying django/db/models/deletion.py -> build/lib/django/db/models copying django/db/models/__init__.py -> build/lib/django/db/models copying django/db/models/options.py -> build/lib/django/db/models copying django/db/models/signals.py -> build/lib/django/db/models copying django/db/models/utils.py -> build/lib/django/db/models copying django/db/models/aggregates.py -> build/lib/django/db/models copying django/db/models/indexes.py -> build/lib/django/db/models creating build/lib/django/db/migrations copying django/db/migrations/graph.py -> build/lib/django/db/migrations copying django/db/migrations/writer.py -> build/lib/django/db/migrations copying django/db/migrations/exceptions.py -> build/lib/django/db/migrations copying django/db/migrations/state.py -> build/lib/django/db/migrations copying django/db/migrations/serializer.py -> build/lib/django/db/migrations copying django/db/migrations/migration.py -> build/lib/django/db/migrations copying django/db/migrations/loader.py -> build/lib/django/db/migrations copying django/db/migrations/optimizer.py -> build/lib/django/db/migrations copying django/db/migrations/autodetector.py -> build/lib/django/db/migrations copying django/db/migrations/questioner.py -> build/lib/django/db/migrations copying django/db/migrations/utils.py -> build/lib/django/db/migrations copying django/db/migrations/__init__.py -> build/lib/django/db/migrations copying django/db/migrations/executor.py -> build/lib/django/db/migrations copying django/db/migrations/recorder.py -> build/lib/django/db/migrations creating build/lib/django/db/backends/mysql copying django/db/backends/mysql/features.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/operations.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/base.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/introspection.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/schema.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/validation.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/creation.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/client.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/compiler.py -> build/lib/django/db/backends/mysql copying django/db/backends/mysql/__init__.py -> build/lib/django/db/backends/mysql creating build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/client.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/features.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/psycopg_any.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/__init__.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/creation.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/operations.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/introspection.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/base.py -> build/lib/django/db/backends/postgresql copying django/db/backends/postgresql/schema.py -> build/lib/django/db/backends/postgresql creating build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/features.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/schema.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/introspection.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/client.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/creation.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/_functions.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/operations.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/base.py -> build/lib/django/db/backends/sqlite3 copying django/db/backends/sqlite3/__init__.py -> build/lib/django/db/backends/sqlite3 creating build/lib/django/db/backends/dummy copying django/db/backends/dummy/base.py -> build/lib/django/db/backends/dummy copying django/db/backends/dummy/__init__.py -> build/lib/django/db/backends/dummy copying django/db/backends/dummy/features.py -> build/lib/django/db/backends/dummy creating build/lib/django/db/backends/base copying django/db/backends/base/validation.py -> build/lib/django/db/backends/base copying django/db/backends/base/client.py -> build/lib/django/db/backends/base copying django/db/backends/base/features.py -> build/lib/django/db/backends/base copying django/db/backends/base/creation.py -> build/lib/django/db/backends/base copying django/db/backends/base/base.py -> build/lib/django/db/backends/base copying django/db/backends/base/introspection.py -> build/lib/django/db/backends/base copying django/db/backends/base/schema.py -> build/lib/django/db/backends/base copying django/db/backends/base/__init__.py -> build/lib/django/db/backends/base copying django/db/backends/base/operations.py -> build/lib/django/db/backends/base creating build/lib/django/db/backends/oracle copying django/db/backends/oracle/base.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/features.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/utils.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/operations.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/schema.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/validation.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/creation.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/client.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/__init__.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/functions.py -> build/lib/django/db/backends/oracle copying django/db/backends/oracle/introspection.py -> build/lib/django/db/backends/oracle creating build/lib/django/db/models/fields copying django/db/models/fields/proxy.py -> build/lib/django/db/models/fields copying django/db/models/fields/related_descriptors.py -> build/lib/django/db/models/fields copying django/db/models/fields/json.py -> build/lib/django/db/models/fields copying django/db/models/fields/related_lookups.py -> build/lib/django/db/models/fields copying django/db/models/fields/mixins.py -> build/lib/django/db/models/fields copying django/db/models/fields/__init__.py -> build/lib/django/db/models/fields copying django/db/models/fields/files.py -> build/lib/django/db/models/fields copying django/db/models/fields/related.py -> build/lib/django/db/models/fields copying django/db/models/fields/reverse_related.py -> build/lib/django/db/models/fields creating build/lib/django/db/models/sql copying django/db/models/sql/where.py -> build/lib/django/db/models/sql copying django/db/models/sql/constants.py -> build/lib/django/db/models/sql copying django/db/models/sql/query.py -> build/lib/django/db/models/sql copying django/db/models/sql/datastructures.py -> build/lib/django/db/models/sql copying django/db/models/sql/subqueries.py -> build/lib/django/db/models/sql copying django/db/models/sql/__init__.py -> build/lib/django/db/models/sql copying django/db/models/sql/compiler.py -> build/lib/django/db/models/sql creating build/lib/django/db/models/functions copying django/db/models/functions/datetime.py -> build/lib/django/db/models/functions copying django/db/models/functions/text.py -> build/lib/django/db/models/functions copying django/db/models/functions/math.py -> build/lib/django/db/models/functions copying django/db/models/functions/mixins.py -> build/lib/django/db/models/functions copying django/db/models/functions/window.py -> build/lib/django/db/models/functions copying django/db/models/functions/__init__.py -> build/lib/django/db/models/functions copying django/db/models/functions/comparison.py -> build/lib/django/db/models/functions creating build/lib/django/db/migrations/operations copying django/db/migrations/operations/special.py -> build/lib/django/db/migrations/operations copying django/db/migrations/operations/fields.py -> build/lib/django/db/migrations/operations copying django/db/migrations/operations/__init__.py -> build/lib/django/db/migrations/operations copying django/db/migrations/operations/base.py -> build/lib/django/db/migrations/operations copying django/db/migrations/operations/models.py -> build/lib/django/db/migrations/operations creating build/lib/django/contrib/gis copying django/contrib/gis/ptr.py -> build/lib/django/contrib/gis copying django/contrib/gis/measure.py -> build/lib/django/contrib/gis copying django/contrib/gis/__init__.py -> build/lib/django/contrib/gis copying django/contrib/gis/feeds.py -> build/lib/django/contrib/gis copying django/contrib/gis/geometry.py -> build/lib/django/contrib/gis copying django/contrib/gis/views.py -> build/lib/django/contrib/gis copying django/contrib/gis/apps.py -> build/lib/django/contrib/gis copying django/contrib/gis/shortcuts.py -> build/lib/django/contrib/gis creating build/lib/django/contrib/flatpages copying django/contrib/flatpages/__init__.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/views.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/apps.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/admin.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/sitemaps.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/middleware.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/models.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/forms.py -> build/lib/django/contrib/flatpages copying django/contrib/flatpages/urls.py -> build/lib/django/contrib/flatpages creating build/lib/django/contrib/sites copying django/contrib/sites/__init__.py -> build/lib/django/contrib/sites copying django/contrib/sites/checks.py -> build/lib/django/contrib/sites copying django/contrib/sites/shortcuts.py -> build/lib/django/contrib/sites copying django/contrib/sites/middleware.py -> build/lib/django/contrib/sites copying django/contrib/sites/managers.py -> build/lib/django/contrib/sites copying django/contrib/sites/management.py -> build/lib/django/contrib/sites copying django/contrib/sites/admin.py -> build/lib/django/contrib/sites copying django/contrib/sites/models.py -> build/lib/django/contrib/sites copying django/contrib/sites/requests.py -> build/lib/django/contrib/sites copying django/contrib/sites/apps.py -> build/lib/django/contrib/sites creating build/lib/django/contrib/sitemaps copying django/contrib/sitemaps/__init__.py -> build/lib/django/contrib/sitemaps copying django/contrib/sitemaps/views.py -> build/lib/django/contrib/sitemaps copying django/contrib/sitemaps/apps.py -> build/lib/django/contrib/sitemaps creating build/lib/django/contrib/auth copying django/contrib/auth/backends.py -> build/lib/django/contrib/auth copying django/contrib/auth/decorators.py -> build/lib/django/contrib/auth copying django/contrib/auth/password_validation.py -> build/lib/django/contrib/auth copying django/contrib/auth/views.py -> build/lib/django/contrib/auth copying django/contrib/auth/urls.py -> build/lib/django/contrib/auth copying django/contrib/auth/checks.py -> build/lib/django/contrib/auth copying django/contrib/auth/admin.py -> build/lib/django/contrib/auth copying django/contrib/auth/tokens.py -> build/lib/django/contrib/auth copying django/contrib/auth/apps.py -> build/lib/django/contrib/auth copying django/contrib/auth/mixins.py -> build/lib/django/contrib/auth copying django/contrib/auth/middleware.py -> build/lib/django/contrib/auth copying django/contrib/auth/validators.py -> build/lib/django/contrib/auth copying django/contrib/auth/__init__.py -> build/lib/django/contrib/auth copying django/contrib/auth/context_processors.py -> build/lib/django/contrib/auth copying django/contrib/auth/models.py -> build/lib/django/contrib/auth copying django/contrib/auth/base_user.py -> build/lib/django/contrib/auth copying django/contrib/auth/forms.py -> build/lib/django/contrib/auth copying django/contrib/auth/signals.py -> build/lib/django/contrib/auth copying django/contrib/auth/hashers.py -> build/lib/django/contrib/auth creating build/lib/django/contrib/messages copying django/contrib/messages/apps.py -> build/lib/django/contrib/messages copying django/contrib/messages/utils.py -> build/lib/django/contrib/messages copying django/contrib/messages/constants.py -> build/lib/django/contrib/messages copying django/contrib/messages/context_processors.py -> build/lib/django/contrib/messages copying django/contrib/messages/middleware.py -> build/lib/django/contrib/messages copying django/contrib/messages/__init__.py -> build/lib/django/contrib/messages copying django/contrib/messages/views.py -> build/lib/django/contrib/messages copying django/contrib/messages/api.py -> build/lib/django/contrib/messages creating build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/storage.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/finders.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/apps.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/utils.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/urls.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/views.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/checks.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/__init__.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/handlers.py -> build/lib/django/contrib/staticfiles copying django/contrib/staticfiles/testing.py -> build/lib/django/contrib/staticfiles creating build/lib/django/contrib/redirects copying django/contrib/redirects/middleware.py -> build/lib/django/contrib/redirects copying django/contrib/redirects/admin.py -> build/lib/django/contrib/redirects copying django/contrib/redirects/apps.py -> build/lib/django/contrib/redirects copying django/contrib/redirects/__init__.py -> build/lib/django/contrib/redirects copying django/contrib/redirects/models.py -> build/lib/django/contrib/redirects creating build/lib/django/contrib/humanize copying django/contrib/humanize/apps.py -> build/lib/django/contrib/humanize copying django/contrib/humanize/__init__.py -> build/lib/django/contrib/humanize creating build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/views.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/admin.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/models.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/fields.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/__init__.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/checks.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/forms.py -> build/lib/django/contrib/contenttypes copying django/contrib/contenttypes/apps.py -> build/lib/django/contrib/contenttypes creating build/lib/django/contrib/sessions copying django/contrib/sessions/exceptions.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/serializers.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/__init__.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/models.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/apps.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/middleware.py -> build/lib/django/contrib/sessions copying django/contrib/sessions/base_session.py -> build/lib/django/contrib/sessions creating build/lib/django/contrib/admin copying django/contrib/admin/exceptions.py -> build/lib/django/contrib/admin copying django/contrib/admin/helpers.py -> build/lib/django/contrib/admin copying django/contrib/admin/checks.py -> build/lib/django/contrib/admin copying django/contrib/admin/decorators.py -> build/lib/django/contrib/admin copying django/contrib/admin/tests.py -> build/lib/django/contrib/admin copying django/contrib/admin/__init__.py -> build/lib/django/contrib/admin copying django/contrib/admin/actions.py -> build/lib/django/contrib/admin copying django/contrib/admin/utils.py -> build/lib/django/contrib/admin copying django/contrib/admin/options.py -> build/lib/django/contrib/admin copying django/contrib/admin/models.py -> build/lib/django/contrib/admin copying django/contrib/admin/apps.py -> build/lib/django/contrib/admin copying django/contrib/admin/sites.py -> build/lib/django/contrib/admin copying django/contrib/admin/forms.py -> build/lib/django/contrib/admin copying django/contrib/admin/widgets.py -> build/lib/django/contrib/admin copying django/contrib/admin/filters.py -> build/lib/django/contrib/admin creating build/lib/django/contrib/postgres copying django/contrib/postgres/operations.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/constraints.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/lookups.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/expressions.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/apps.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/utils.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/__init__.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/search.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/validators.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/indexes.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/signals.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/functions.py -> build/lib/django/contrib/postgres copying django/contrib/postgres/serializers.py -> build/lib/django/contrib/postgres creating build/lib/django/contrib/syndication copying django/contrib/syndication/__init__.py -> build/lib/django/contrib/syndication copying django/contrib/syndication/views.py -> build/lib/django/contrib/syndication copying django/contrib/syndication/apps.py -> build/lib/django/contrib/syndication creating build/lib/django/contrib/admindocs copying django/contrib/admindocs/__init__.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/views.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/utils.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/urls.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/apps.py -> build/lib/django/contrib/admindocs copying django/contrib/admindocs/middleware.py -> build/lib/django/contrib/admindocs creating build/lib/django/contrib/gis/forms copying django/contrib/gis/forms/widgets.py -> build/lib/django/contrib/gis/forms copying django/contrib/gis/forms/__init__.py -> build/lib/django/contrib/gis/forms copying django/contrib/gis/forms/fields.py -> build/lib/django/contrib/gis/forms creating build/lib/django/contrib/gis/serializers copying django/contrib/gis/serializers/geojson.py -> build/lib/django/contrib/gis/serializers copying django/contrib/gis/serializers/__init__.py -> build/lib/django/contrib/gis/serializers creating build/lib/django/contrib/gis/management copying django/contrib/gis/management/__init__.py -> build/lib/django/contrib/gis/management creating build/lib/django/contrib/gis/admin copying django/contrib/gis/admin/__init__.py -> build/lib/django/contrib/gis/admin copying django/contrib/gis/admin/widgets.py -> build/lib/django/contrib/gis/admin copying django/contrib/gis/admin/options.py -> build/lib/django/contrib/gis/admin creating build/lib/django/contrib/gis/db copying django/contrib/gis/db/__init__.py -> build/lib/django/contrib/gis/db creating build/lib/django/contrib/gis/sitemaps copying django/contrib/gis/sitemaps/views.py -> build/lib/django/contrib/gis/sitemaps copying django/contrib/gis/sitemaps/__init__.py -> build/lib/django/contrib/gis/sitemaps copying django/contrib/gis/sitemaps/kml.py -> build/lib/django/contrib/gis/sitemaps creating build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/geometries.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/base.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/__init__.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/field.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/datasource.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/driver.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/geomtype.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/layer.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/error.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/srs.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/envelope.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/libgdal.py -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/gdal/feature.py -> build/lib/django/contrib/gis/gdal creating build/lib/django/contrib/gis/utils copying django/contrib/gis/utils/srs.py -> build/lib/django/contrib/gis/utils copying django/contrib/gis/utils/ogrinspect.py -> build/lib/django/contrib/gis/utils copying django/contrib/gis/utils/ogrinfo.py -> build/lib/django/contrib/gis/utils copying django/contrib/gis/utils/layermapping.py -> build/lib/django/contrib/gis/utils copying django/contrib/gis/utils/__init__.py -> build/lib/django/contrib/gis/utils creating build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/io.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/coordseq.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/mutable_list.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/factory.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/__init__.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/base.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/linestring.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/collections.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/prepared.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/error.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/polygon.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/geometry.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/point.py -> build/lib/django/contrib/gis/geos copying django/contrib/gis/geos/libgeos.py -> build/lib/django/contrib/gis/geos creating build/lib/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/base.py -> build/lib/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/resources.py -> build/lib/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/__init__.py -> build/lib/django/contrib/gis/geoip2 creating build/lib/django/contrib/gis/management/commands copying django/contrib/gis/management/commands/__init__.py -> build/lib/django/contrib/gis/management/commands copying django/contrib/gis/management/commands/ogrinspect.py -> build/lib/django/contrib/gis/management/commands copying django/contrib/gis/management/commands/inspectdb.py -> build/lib/django/contrib/gis/management/commands creating build/lib/django/contrib/gis/db/backends copying django/contrib/gis/db/backends/utils.py -> build/lib/django/contrib/gis/db/backends copying django/contrib/gis/db/backends/__init__.py -> build/lib/django/contrib/gis/db/backends creating build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/lookups.py -> build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/__init__.py -> build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/aggregates.py -> build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/proxy.py -> build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/functions.py -> build/lib/django/contrib/gis/db/models copying django/contrib/gis/db/models/fields.py -> build/lib/django/contrib/gis/db/models creating build/lib/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/schema.py -> build/lib/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/operations.py -> build/lib/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/introspection.py -> build/lib/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/__init__.py -> build/lib/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/features.py -> build/lib/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/base.py -> build/lib/django/contrib/gis/db/backends/mysql creating build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/features.py -> build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/operations.py -> build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/adapter.py -> build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/models.py -> build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/base.py -> build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/schema.py -> build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/__init__.py -> build/lib/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/introspection.py -> build/lib/django/contrib/gis/db/backends/oracle creating build/lib/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/models.py -> build/lib/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/features.py -> build/lib/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/adapter.py -> build/lib/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/__init__.py -> build/lib/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/operations.py -> build/lib/django/contrib/gis/db/backends/base creating build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/adapter.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/introspection.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/client.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/base.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/__init__.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/models.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/features.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/schema.py -> build/lib/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/operations.py -> build/lib/django/contrib/gis/db/backends/spatialite creating build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/__init__.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/operations.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/base.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/models.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/introspection.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/schema.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/pgraster.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/const.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/adapter.py -> build/lib/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/features.py -> build/lib/django/contrib/gis/db/backends/postgis creating build/lib/django/contrib/gis/db/models/sql copying django/contrib/gis/db/models/sql/__init__.py -> build/lib/django/contrib/gis/db/models/sql copying django/contrib/gis/db/models/sql/conversion.py -> build/lib/django/contrib/gis/db/models/sql creating build/lib/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/source.py -> build/lib/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/__init__.py -> build/lib/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/band.py -> build/lib/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/const.py -> build/lib/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/base.py -> build/lib/django/contrib/gis/gdal/raster creating build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/errcheck.py -> build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/srs.py -> build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/generation.py -> build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/ds.py -> build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/geom.py -> build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/raster.py -> build/lib/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/__init__.py -> build/lib/django/contrib/gis/gdal/prototypes creating build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/__init__.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/topology.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/coordseq.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/prepared.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/predicates.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/threadsafe.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/io.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/errcheck.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/misc.py -> build/lib/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/geom.py -> build/lib/django/contrib/gis/geos/prototypes creating build/lib/django/contrib/flatpages/migrations copying django/contrib/flatpages/migrations/__init__.py -> build/lib/django/contrib/flatpages/migrations copying django/contrib/flatpages/migrations/0001_initial.py -> build/lib/django/contrib/flatpages/migrations creating build/lib/django/contrib/flatpages/templatetags copying django/contrib/flatpages/templatetags/__init__.py -> build/lib/django/contrib/flatpages/templatetags copying django/contrib/flatpages/templatetags/flatpages.py -> build/lib/django/contrib/flatpages/templatetags creating build/lib/django/contrib/sites/migrations copying django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/lib/django/contrib/sites/migrations copying django/contrib/sites/migrations/0001_initial.py -> build/lib/django/contrib/sites/migrations copying django/contrib/sites/migrations/__init__.py -> build/lib/django/contrib/sites/migrations creating build/lib/django/contrib/sitemaps/management copying django/contrib/sitemaps/management/__init__.py -> build/lib/django/contrib/sitemaps/management creating build/lib/django/contrib/sitemaps/management/commands copying django/contrib/sitemaps/management/commands/__init__.py -> build/lib/django/contrib/sitemaps/management/commands copying django/contrib/sitemaps/management/commands/ping_google.py -> build/lib/django/contrib/sitemaps/management/commands creating build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/__init__.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0001_initial.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/lib/django/contrib/auth/migrations copying django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/lib/django/contrib/auth/migrations creating build/lib/django/contrib/auth/handlers copying django/contrib/auth/handlers/__init__.py -> build/lib/django/contrib/auth/handlers copying django/contrib/auth/handlers/modwsgi.py -> build/lib/django/contrib/auth/handlers creating build/lib/django/contrib/auth/management copying django/contrib/auth/management/__init__.py -> build/lib/django/contrib/auth/management creating build/lib/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/__init__.py -> build/lib/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/createsuperuser.py -> build/lib/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/changepassword.py -> build/lib/django/contrib/auth/management/commands creating build/lib/django/contrib/messages/storage copying django/contrib/messages/storage/session.py -> build/lib/django/contrib/messages/storage copying django/contrib/messages/storage/base.py -> build/lib/django/contrib/messages/storage copying django/contrib/messages/storage/fallback.py -> build/lib/django/contrib/messages/storage copying django/contrib/messages/storage/__init__.py -> build/lib/django/contrib/messages/storage copying django/contrib/messages/storage/cookie.py -> build/lib/django/contrib/messages/storage creating build/lib/django/contrib/staticfiles/management copying django/contrib/staticfiles/management/__init__.py -> build/lib/django/contrib/staticfiles/management creating build/lib/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/__init__.py -> build/lib/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/findstatic.py -> build/lib/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/collectstatic.py -> build/lib/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/runserver.py -> build/lib/django/contrib/staticfiles/management/commands creating build/lib/django/contrib/redirects/migrations copying django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/lib/django/contrib/redirects/migrations copying django/contrib/redirects/migrations/__init__.py -> build/lib/django/contrib/redirects/migrations copying django/contrib/redirects/migrations/0001_initial.py -> build/lib/django/contrib/redirects/migrations creating build/lib/django/contrib/humanize/templatetags copying django/contrib/humanize/templatetags/humanize.py -> build/lib/django/contrib/humanize/templatetags copying django/contrib/humanize/templatetags/__init__.py -> build/lib/django/contrib/humanize/templatetags creating build/lib/django/contrib/contenttypes/migrations copying django/contrib/contenttypes/migrations/0001_initial.py -> build/lib/django/contrib/contenttypes/migrations copying django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/lib/django/contrib/contenttypes/migrations copying django/contrib/contenttypes/migrations/__init__.py -> build/lib/django/contrib/contenttypes/migrations creating build/lib/django/contrib/contenttypes/management copying django/contrib/contenttypes/management/__init__.py -> build/lib/django/contrib/contenttypes/management creating build/lib/django/contrib/contenttypes/management/commands copying django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/lib/django/contrib/contenttypes/management/commands copying django/contrib/contenttypes/management/commands/__init__.py -> build/lib/django/contrib/contenttypes/management/commands creating build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/base.py -> build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/file.py -> build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/signed_cookies.py -> build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/__init__.py -> build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/cache.py -> build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/db.py -> build/lib/django/contrib/sessions/backends copying django/contrib/sessions/backends/cached_db.py -> build/lib/django/contrib/sessions/backends creating build/lib/django/contrib/sessions/management copying django/contrib/sessions/management/__init__.py -> build/lib/django/contrib/sessions/management creating build/lib/django/contrib/sessions/migrations copying django/contrib/sessions/migrations/__init__.py -> build/lib/django/contrib/sessions/migrations copying django/contrib/sessions/migrations/0001_initial.py -> build/lib/django/contrib/sessions/migrations creating build/lib/django/contrib/sessions/management/commands copying django/contrib/sessions/management/commands/clearsessions.py -> build/lib/django/contrib/sessions/management/commands copying django/contrib/sessions/management/commands/__init__.py -> build/lib/django/contrib/sessions/management/commands creating build/lib/django/contrib/admin/views copying django/contrib/admin/views/__init__.py -> build/lib/django/contrib/admin/views copying django/contrib/admin/views/decorators.py -> build/lib/django/contrib/admin/views copying django/contrib/admin/views/autocomplete.py -> build/lib/django/contrib/admin/views copying django/contrib/admin/views/main.py -> build/lib/django/contrib/admin/views creating build/lib/django/contrib/admin/migrations copying django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/lib/django/contrib/admin/migrations copying django/contrib/admin/migrations/__init__.py -> build/lib/django/contrib/admin/migrations copying django/contrib/admin/migrations/0001_initial.py -> build/lib/django/contrib/admin/migrations copying django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/lib/django/contrib/admin/migrations creating build/lib/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/admin_modify.py -> build/lib/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/__init__.py -> build/lib/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/log.py -> build/lib/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/admin_list.py -> build/lib/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/base.py -> build/lib/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/admin_urls.py -> build/lib/django/contrib/admin/templatetags creating build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/ranges.py -> build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/array.py -> build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/citext.py -> build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/__init__.py -> build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/utils.py -> build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/hstore.py -> build/lib/django/contrib/postgres/fields copying django/contrib/postgres/fields/jsonb.py -> build/lib/django/contrib/postgres/fields creating build/lib/django/contrib/postgres/forms copying django/contrib/postgres/forms/ranges.py -> build/lib/django/contrib/postgres/forms copying django/contrib/postgres/forms/array.py -> build/lib/django/contrib/postgres/forms copying django/contrib/postgres/forms/hstore.py -> build/lib/django/contrib/postgres/forms copying django/contrib/postgres/forms/__init__.py -> build/lib/django/contrib/postgres/forms creating build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/statistics.py -> build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/mixins.py -> build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/general.py -> build/lib/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/__init__.py -> build/lib/django/contrib/postgres/aggregates creating build/lib/django/conf/urls copying django/conf/urls/i18n.py -> build/lib/django/conf/urls copying django/conf/urls/static.py -> build/lib/django/conf/urls copying django/conf/urls/__init__.py -> build/lib/django/conf/urls creating build/lib/django/conf/locale copying django/conf/locale/__init__.py -> build/lib/django/conf/locale creating build/lib/django/conf/locale/ms copying django/conf/locale/ms/__init__.py -> build/lib/django/conf/locale/ms copying django/conf/locale/ms/formats.py -> build/lib/django/conf/locale/ms creating build/lib/django/conf/locale/gl copying django/conf/locale/gl/formats.py -> build/lib/django/conf/locale/gl copying django/conf/locale/gl/__init__.py -> build/lib/django/conf/locale/gl creating build/lib/django/conf/locale/sr_Latn copying django/conf/locale/sr_Latn/formats.py -> build/lib/django/conf/locale/sr_Latn copying django/conf/locale/sr_Latn/__init__.py -> build/lib/django/conf/locale/sr_Latn creating build/lib/django/conf/locale/pt_BR copying django/conf/locale/pt_BR/formats.py -> build/lib/django/conf/locale/pt_BR copying django/conf/locale/pt_BR/__init__.py -> build/lib/django/conf/locale/pt_BR creating build/lib/django/conf/locale/pl copying django/conf/locale/pl/formats.py -> build/lib/django/conf/locale/pl copying django/conf/locale/pl/__init__.py -> build/lib/django/conf/locale/pl creating build/lib/django/conf/locale/es copying django/conf/locale/es/formats.py -> build/lib/django/conf/locale/es copying django/conf/locale/es/__init__.py -> build/lib/django/conf/locale/es creating build/lib/django/conf/locale/hu copying django/conf/locale/hu/formats.py -> build/lib/django/conf/locale/hu copying django/conf/locale/hu/__init__.py -> build/lib/django/conf/locale/hu creating build/lib/django/conf/locale/hr copying django/conf/locale/hr/formats.py -> build/lib/django/conf/locale/hr copying django/conf/locale/hr/__init__.py -> build/lib/django/conf/locale/hr creating build/lib/django/conf/locale/de_CH copying django/conf/locale/de_CH/__init__.py -> build/lib/django/conf/locale/de_CH copying django/conf/locale/de_CH/formats.py -> build/lib/django/conf/locale/de_CH creating build/lib/django/conf/locale/et copying django/conf/locale/et/__init__.py -> build/lib/django/conf/locale/et copying django/conf/locale/et/formats.py -> build/lib/django/conf/locale/et creating build/lib/django/conf/locale/bs copying django/conf/locale/bs/formats.py -> build/lib/django/conf/locale/bs copying django/conf/locale/bs/__init__.py -> build/lib/django/conf/locale/bs creating build/lib/django/conf/locale/kn copying django/conf/locale/kn/formats.py -> build/lib/django/conf/locale/kn copying django/conf/locale/kn/__init__.py -> build/lib/django/conf/locale/kn creating build/lib/django/conf/locale/bg copying django/conf/locale/bg/__init__.py -> build/lib/django/conf/locale/bg copying django/conf/locale/bg/formats.py -> build/lib/django/conf/locale/bg creating build/lib/django/conf/locale/ar_DZ copying django/conf/locale/ar_DZ/__init__.py -> build/lib/django/conf/locale/ar_DZ copying django/conf/locale/ar_DZ/formats.py -> build/lib/django/conf/locale/ar_DZ creating build/lib/django/conf/locale/nb copying django/conf/locale/nb/__init__.py -> build/lib/django/conf/locale/nb copying django/conf/locale/nb/formats.py -> build/lib/django/conf/locale/nb creating build/lib/django/conf/locale/ga copying django/conf/locale/ga/formats.py -> build/lib/django/conf/locale/ga copying django/conf/locale/ga/__init__.py -> build/lib/django/conf/locale/ga creating build/lib/django/conf/locale/mn copying django/conf/locale/mn/formats.py -> build/lib/django/conf/locale/mn copying django/conf/locale/mn/__init__.py -> build/lib/django/conf/locale/mn creating build/lib/django/conf/locale/es_CO copying django/conf/locale/es_CO/__init__.py -> build/lib/django/conf/locale/es_CO copying django/conf/locale/es_CO/formats.py -> build/lib/django/conf/locale/es_CO creating build/lib/django/conf/locale/nl copying django/conf/locale/nl/formats.py -> build/lib/django/conf/locale/nl copying django/conf/locale/nl/__init__.py -> build/lib/django/conf/locale/nl creating build/lib/django/conf/locale/es_NI copying django/conf/locale/es_NI/__init__.py -> build/lib/django/conf/locale/es_NI copying django/conf/locale/es_NI/formats.py -> build/lib/django/conf/locale/es_NI creating build/lib/django/conf/locale/en copying django/conf/locale/en/formats.py -> build/lib/django/conf/locale/en copying django/conf/locale/en/__init__.py -> build/lib/django/conf/locale/en creating build/lib/django/conf/locale/fr copying django/conf/locale/fr/__init__.py -> build/lib/django/conf/locale/fr copying django/conf/locale/fr/formats.py -> build/lib/django/conf/locale/fr creating build/lib/django/conf/locale/en_AU copying django/conf/locale/en_AU/formats.py -> build/lib/django/conf/locale/en_AU copying django/conf/locale/en_AU/__init__.py -> build/lib/django/conf/locale/en_AU creating build/lib/django/conf/locale/he copying django/conf/locale/he/formats.py -> build/lib/django/conf/locale/he copying django/conf/locale/he/__init__.py -> build/lib/django/conf/locale/he creating build/lib/django/conf/locale/fa copying django/conf/locale/fa/__init__.py -> build/lib/django/conf/locale/fa copying django/conf/locale/fa/formats.py -> build/lib/django/conf/locale/fa creating build/lib/django/conf/locale/tg copying django/conf/locale/tg/formats.py -> build/lib/django/conf/locale/tg copying django/conf/locale/tg/__init__.py -> build/lib/django/conf/locale/tg creating build/lib/django/conf/locale/ar copying django/conf/locale/ar/__init__.py -> build/lib/django/conf/locale/ar copying django/conf/locale/ar/formats.py -> build/lib/django/conf/locale/ar creating build/lib/django/conf/locale/bn copying django/conf/locale/bn/formats.py -> build/lib/django/conf/locale/bn copying django/conf/locale/bn/__init__.py -> build/lib/django/conf/locale/bn creating build/lib/django/conf/locale/km copying django/conf/locale/km/__init__.py -> build/lib/django/conf/locale/km copying django/conf/locale/km/formats.py -> build/lib/django/conf/locale/km creating build/lib/django/conf/locale/ky copying django/conf/locale/ky/formats.py -> build/lib/django/conf/locale/ky copying django/conf/locale/ky/__init__.py -> build/lib/django/conf/locale/ky creating build/lib/django/conf/locale/lt copying django/conf/locale/lt/__init__.py -> build/lib/django/conf/locale/lt copying django/conf/locale/lt/formats.py -> build/lib/django/conf/locale/lt creating build/lib/django/conf/locale/uz copying django/conf/locale/uz/__init__.py -> build/lib/django/conf/locale/uz copying django/conf/locale/uz/formats.py -> build/lib/django/conf/locale/uz creating build/lib/django/conf/locale/en_GB copying django/conf/locale/en_GB/formats.py -> build/lib/django/conf/locale/en_GB copying django/conf/locale/en_GB/__init__.py -> build/lib/django/conf/locale/en_GB creating build/lib/django/conf/locale/es_MX copying django/conf/locale/es_MX/__init__.py -> build/lib/django/conf/locale/es_MX copying django/conf/locale/es_MX/formats.py -> build/lib/django/conf/locale/es_MX creating build/lib/django/conf/locale/cy copying django/conf/locale/cy/__init__.py -> build/lib/django/conf/locale/cy copying django/conf/locale/cy/formats.py -> build/lib/django/conf/locale/cy creating build/lib/django/conf/locale/cs copying django/conf/locale/cs/formats.py -> build/lib/django/conf/locale/cs copying django/conf/locale/cs/__init__.py -> build/lib/django/conf/locale/cs creating build/lib/django/conf/locale/zh_Hant copying django/conf/locale/zh_Hant/__init__.py -> build/lib/django/conf/locale/zh_Hant copying django/conf/locale/zh_Hant/formats.py -> build/lib/django/conf/locale/zh_Hant creating build/lib/django/conf/locale/ru copying django/conf/locale/ru/formats.py -> build/lib/django/conf/locale/ru copying django/conf/locale/ru/__init__.py -> build/lib/django/conf/locale/ru creating build/lib/django/conf/locale/id copying django/conf/locale/id/formats.py -> build/lib/django/conf/locale/id copying django/conf/locale/id/__init__.py -> build/lib/django/conf/locale/id creating build/lib/django/conf/locale/mk copying django/conf/locale/mk/__init__.py -> build/lib/django/conf/locale/mk copying django/conf/locale/mk/formats.py -> build/lib/django/conf/locale/mk creating build/lib/django/conf/locale/te copying django/conf/locale/te/__init__.py -> build/lib/django/conf/locale/te copying django/conf/locale/te/formats.py -> build/lib/django/conf/locale/te creating build/lib/django/conf/locale/az copying django/conf/locale/az/__init__.py -> build/lib/django/conf/locale/az copying django/conf/locale/az/formats.py -> build/lib/django/conf/locale/az creating build/lib/django/conf/locale/fi copying django/conf/locale/fi/formats.py -> build/lib/django/conf/locale/fi copying django/conf/locale/fi/__init__.py -> build/lib/django/conf/locale/fi creating build/lib/django/conf/locale/sv copying django/conf/locale/sv/formats.py -> build/lib/django/conf/locale/sv copying django/conf/locale/sv/__init__.py -> build/lib/django/conf/locale/sv creating build/lib/django/conf/locale/eu copying django/conf/locale/eu/formats.py -> build/lib/django/conf/locale/eu copying django/conf/locale/eu/__init__.py -> build/lib/django/conf/locale/eu creating build/lib/django/conf/locale/lv copying django/conf/locale/lv/formats.py -> build/lib/django/conf/locale/lv copying django/conf/locale/lv/__init__.py -> build/lib/django/conf/locale/lv creating build/lib/django/conf/locale/pt copying django/conf/locale/pt/__init__.py -> build/lib/django/conf/locale/pt copying django/conf/locale/pt/formats.py -> build/lib/django/conf/locale/pt creating build/lib/django/conf/locale/ko copying django/conf/locale/ko/__init__.py -> build/lib/django/conf/locale/ko copying django/conf/locale/ko/formats.py -> build/lib/django/conf/locale/ko creating build/lib/django/conf/locale/el copying django/conf/locale/el/__init__.py -> build/lib/django/conf/locale/el copying django/conf/locale/el/formats.py -> build/lib/django/conf/locale/el creating build/lib/django/conf/locale/sq copying django/conf/locale/sq/formats.py -> build/lib/django/conf/locale/sq copying django/conf/locale/sq/__init__.py -> build/lib/django/conf/locale/sq creating build/lib/django/conf/locale/es_AR copying django/conf/locale/es_AR/__init__.py -> build/lib/django/conf/locale/es_AR copying django/conf/locale/es_AR/formats.py -> build/lib/django/conf/locale/es_AR creating build/lib/django/conf/locale/th copying django/conf/locale/th/__init__.py -> build/lib/django/conf/locale/th copying django/conf/locale/th/formats.py -> build/lib/django/conf/locale/th creating build/lib/django/conf/locale/ml copying django/conf/locale/ml/__init__.py -> build/lib/django/conf/locale/ml copying django/conf/locale/ml/formats.py -> build/lib/django/conf/locale/ml creating build/lib/django/conf/locale/de copying django/conf/locale/de/formats.py -> build/lib/django/conf/locale/de copying django/conf/locale/de/__init__.py -> build/lib/django/conf/locale/de creating build/lib/django/conf/locale/ja copying django/conf/locale/ja/formats.py -> build/lib/django/conf/locale/ja copying django/conf/locale/ja/__init__.py -> build/lib/django/conf/locale/ja creating build/lib/django/conf/locale/vi copying django/conf/locale/vi/__init__.py -> build/lib/django/conf/locale/vi copying django/conf/locale/vi/formats.py -> build/lib/django/conf/locale/vi creating build/lib/django/conf/locale/nn copying django/conf/locale/nn/__init__.py -> build/lib/django/conf/locale/nn copying django/conf/locale/nn/formats.py -> build/lib/django/conf/locale/nn creating build/lib/django/conf/locale/zh_Hans copying django/conf/locale/zh_Hans/formats.py -> build/lib/django/conf/locale/zh_Hans copying django/conf/locale/zh_Hans/__init__.py -> build/lib/django/conf/locale/zh_Hans creating build/lib/django/conf/locale/uk copying django/conf/locale/uk/__init__.py -> build/lib/django/conf/locale/uk copying django/conf/locale/uk/formats.py -> build/lib/django/conf/locale/uk creating build/lib/django/conf/locale/ig copying django/conf/locale/ig/__init__.py -> build/lib/django/conf/locale/ig copying django/conf/locale/ig/formats.py -> build/lib/django/conf/locale/ig creating build/lib/django/conf/locale/is copying django/conf/locale/is/__init__.py -> build/lib/django/conf/locale/is copying django/conf/locale/is/formats.py -> build/lib/django/conf/locale/is creating build/lib/django/conf/locale/da copying django/conf/locale/da/formats.py -> build/lib/django/conf/locale/da copying django/conf/locale/da/__init__.py -> build/lib/django/conf/locale/da creating build/lib/django/conf/locale/tr copying django/conf/locale/tr/formats.py -> build/lib/django/conf/locale/tr copying django/conf/locale/tr/__init__.py -> build/lib/django/conf/locale/tr creating build/lib/django/conf/locale/sk copying django/conf/locale/sk/formats.py -> build/lib/django/conf/locale/sk copying django/conf/locale/sk/__init__.py -> build/lib/django/conf/locale/sk creating build/lib/django/conf/locale/es_PR copying django/conf/locale/es_PR/__init__.py -> build/lib/django/conf/locale/es_PR copying django/conf/locale/es_PR/formats.py -> build/lib/django/conf/locale/es_PR creating build/lib/django/conf/locale/eo copying django/conf/locale/eo/formats.py -> build/lib/django/conf/locale/eo copying django/conf/locale/eo/__init__.py -> build/lib/django/conf/locale/eo creating build/lib/django/conf/locale/ka copying django/conf/locale/ka/formats.py -> build/lib/django/conf/locale/ka copying django/conf/locale/ka/__init__.py -> build/lib/django/conf/locale/ka creating build/lib/django/conf/locale/sl copying django/conf/locale/sl/formats.py -> build/lib/django/conf/locale/sl copying django/conf/locale/sl/__init__.py -> build/lib/django/conf/locale/sl creating build/lib/django/conf/locale/tk copying django/conf/locale/tk/__init__.py -> build/lib/django/conf/locale/tk copying django/conf/locale/tk/formats.py -> build/lib/django/conf/locale/tk creating build/lib/django/conf/locale/fy copying django/conf/locale/fy/__init__.py -> build/lib/django/conf/locale/fy copying django/conf/locale/fy/formats.py -> build/lib/django/conf/locale/fy creating build/lib/django/conf/locale/ta copying django/conf/locale/ta/__init__.py -> build/lib/django/conf/locale/ta copying django/conf/locale/ta/formats.py -> build/lib/django/conf/locale/ta creating build/lib/django/conf/locale/sr copying django/conf/locale/sr/__init__.py -> build/lib/django/conf/locale/sr copying django/conf/locale/sr/formats.py -> build/lib/django/conf/locale/sr creating build/lib/django/conf/locale/hi copying django/conf/locale/hi/formats.py -> build/lib/django/conf/locale/hi copying django/conf/locale/hi/__init__.py -> build/lib/django/conf/locale/hi creating build/lib/django/conf/locale/ckb copying django/conf/locale/ckb/formats.py -> build/lib/django/conf/locale/ckb copying django/conf/locale/ckb/__init__.py -> build/lib/django/conf/locale/ckb creating build/lib/django/conf/locale/ca copying django/conf/locale/ca/formats.py -> build/lib/django/conf/locale/ca copying django/conf/locale/ca/__init__.py -> build/lib/django/conf/locale/ca creating build/lib/django/conf/locale/ro copying django/conf/locale/ro/__init__.py -> build/lib/django/conf/locale/ro copying django/conf/locale/ro/formats.py -> build/lib/django/conf/locale/ro creating build/lib/django/conf/locale/it copying django/conf/locale/it/formats.py -> build/lib/django/conf/locale/it copying django/conf/locale/it/__init__.py -> build/lib/django/conf/locale/it creating build/lib/django/conf/locale/gd copying django/conf/locale/gd/__init__.py -> build/lib/django/conf/locale/gd copying django/conf/locale/gd/formats.py -> build/lib/django/conf/locale/gd running egg_info writing Django.egg-info/PKG-INFO writing dependency_links to Django.egg-info/dependency_links.txt writing entry points to Django.egg-info/entry_points.txt writing requirements to Django.egg-info/requires.txt writing top-level names to Django.egg-info/top_level.txt reading manifest file 'Django.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found anywhere in distribution adding license file 'LICENSE' adding license file 'LICENSE.python' adding license file 'AUTHORS' writing manifest file 'Django.egg-info/SOURCES.txt' /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.app_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.app_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.app_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.app_template' to be distributed and are already explicitly excluding 'django.conf.app_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.app_template.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.app_template.migrations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.app_template.migrations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.app_template.migrations' to be distributed and are already explicitly excluding 'django.conf.app_template.migrations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ig.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ig.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ig.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ig.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ig.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.conf.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.project_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.project_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.project_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.project_template' to be distributed and are already explicitly excluding 'django.conf.project_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.project_template.project_name' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.conf.project_template.project_name' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.conf.project_template.project_name' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.conf.project_template.project_name' to be distributed and are already explicitly excluding 'django.conf.project_template.project_name' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.am.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.am.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.am.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.am.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.am.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.css' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.css.vendor.select2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.css.vendor.select2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.css.vendor.select2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.css.vendor.select2' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.css.vendor.select2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.img' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.img.gis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.img.gis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.img.gis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.img.gis' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.img.gis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.admin' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.jquery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.jquery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.jquery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.jquery' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.jquery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.select2' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2.i18n' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.select2.i18n' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2.i18n' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.xregexp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.js.vendor.xregexp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.static.admin.js.vendor.xregexp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.static.admin.js.vendor.xregexp' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.xregexp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.auth.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.auth.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.auth.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.auth.user' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.auth.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.edit_inline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.edit_inline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.edit_inline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.edit_inline' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.edit_inline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.includes' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.admin.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.admin.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.admin.widgets' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.admin.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.registration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.templates.registration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admin.templates.registration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admin.templates.registration' to be distributed and are already explicitly excluding 'django.contrib.admin.templates.registration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.templates.admin_doc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admindocs.templates.admin_doc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.admindocs.templates.admin_doc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.admindocs.templates.admin_doc' to be distributed and are already explicitly excluding 'django.contrib.admindocs.templates.admin_doc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.templates.auth.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.templates.auth.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.templates.auth.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.templates.auth.widgets' to be distributed and are already explicitly excluding 'django.contrib.auth.templates.auth.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.templates.registration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.auth.templates.registration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.auth.templates.registration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.auth.templates.registration' to be distributed and are already explicitly excluding 'django.contrib.auth.templates.registration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.static.gis.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.static.gis.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.static.gis.css' to be distributed and are already explicitly excluding 'django.contrib.gis.static.gis.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.static.gis.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.static.gis.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.static.gis.img' to be distributed and are already explicitly excluding 'django.contrib.gis.static.gis.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.static.gis.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.static.gis.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.static.gis.js' to be distributed and are already explicitly excluding 'django.contrib.gis.static.gis.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.templates.gis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.templates.gis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.templates.gis' to be distributed and are already explicitly excluding 'django.contrib.gis.templates.gis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.templates.gis.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.templates.gis.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.templates.gis.admin' to be distributed and are already explicitly excluding 'django.contrib.gis.templates.gis.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis.kml' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.gis.templates.gis.kml' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.gis.templates.gis.kml' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.gis.templates.gis.kml' to be distributed and are already explicitly excluding 'django.contrib.gis.templates.gis.kml' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.jinja2.postgres.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.jinja2.postgres.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.jinja2.postgres.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.jinja2.postgres.widgets' to be distributed and are already explicitly excluding 'django.contrib.postgres.jinja2.postgres.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.templates.postgres.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.postgres.templates.postgres.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.postgres.templates.postgres.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.postgres.templates.postgres.widgets' to be distributed and are already explicitly excluding 'django.contrib.postgres.templates.postgres.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sitemaps.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sitemaps.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sitemaps.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sitemaps.templates' to be distributed and are already explicitly excluding 'django.contrib.sitemaps.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ast.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ast.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ckb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ckb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.dsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.dsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.dsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.dsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.en_AU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_CO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_CO.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_CO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.es_VE.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.es_VE.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.es_VE.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.fy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.fy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hsb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hsb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hsb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hsb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.io.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.io.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.io.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.io.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.io.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kab.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.kab.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.kab.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.kab.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.kab.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.lb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.lb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.mr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.mr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.my.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.my.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.os.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.os.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.udm.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.udm.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.udm.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.udm.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.udm.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.uz.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.uz.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.errors.dict' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.errors.dict' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.errors.dict' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.errors.dict' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.errors.dict' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.errors.list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.errors.list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.errors.list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.errors.list' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.errors.list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.formsets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.formsets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.formsets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.formsets' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.formsets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.jinja2.django.forms.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.jinja2.django.forms.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.jinja2.django.forms.widgets' to be distributed and are already explicitly excluding 'django.forms.jinja2.django.forms.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.errors.dict' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.errors.dict' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.errors.dict' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.errors.dict' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.errors.dict' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.errors.list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.errors.list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.errors.list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.errors.list' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.errors.list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.formsets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.formsets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.formsets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.formsets' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.formsets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.forms.templates.django.forms.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.forms.templates.django.forms.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.forms.templates.django.forms.widgets' to be distributed and are already explicitly excluding 'django.forms.templates.django.forms.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.views.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.views.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.views.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.views.templates' to be distributed and are already explicitly excluding 'django.views.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/django/views/templates copying django/views/templates/default_urlconf.html -> build/lib/django/views/templates copying django/views/templates/technical_404.html -> build/lib/django/views/templates copying django/views/templates/technical_500.html -> build/lib/django/views/templates copying django/views/templates/technical_500.txt -> build/lib/django/views/templates creating build/lib/django/forms/jinja2 creating build/lib/django/forms/jinja2/django creating build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/attrs.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/default.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/div.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/label.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/p.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/table.html -> build/lib/django/forms/jinja2/django/forms copying django/forms/jinja2/django/forms/ul.html -> build/lib/django/forms/jinja2/django/forms creating build/lib/django/forms/jinja2/django/forms/errors creating build/lib/django/forms/jinja2/django/forms/errors/dict copying django/forms/jinja2/django/forms/errors/dict/default.html -> build/lib/django/forms/jinja2/django/forms/errors/dict copying django/forms/jinja2/django/forms/errors/dict/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/dict copying django/forms/jinja2/django/forms/errors/dict/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/dict creating build/lib/django/forms/jinja2/django/forms/errors/list copying django/forms/jinja2/django/forms/errors/list/default.html -> build/lib/django/forms/jinja2/django/forms/errors/list copying django/forms/jinja2/django/forms/errors/list/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/list copying django/forms/jinja2/django/forms/errors/list/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/list creating build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/default.html -> build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/div.html -> build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/p.html -> build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/table.html -> build/lib/django/forms/jinja2/django/forms/formsets copying django/forms/jinja2/django/forms/formsets/ul.html -> build/lib/django/forms/jinja2/django/forms/formsets creating build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/attrs.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/checkbox.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/date.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/datetime.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/email.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/file.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/input.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/input_option.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/number.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/password.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/radio.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/radio_option.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/select.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/select_date.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/select_option.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/text.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/textarea.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/time.html -> build/lib/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/url.html -> build/lib/django/forms/jinja2/django/forms/widgets creating build/lib/django/forms/templates creating build/lib/django/forms/templates/django creating build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/attrs.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/default.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/div.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/label.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/p.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/table.html -> build/lib/django/forms/templates/django/forms copying django/forms/templates/django/forms/ul.html -> build/lib/django/forms/templates/django/forms creating build/lib/django/forms/templates/django/forms/errors creating build/lib/django/forms/templates/django/forms/errors/dict copying django/forms/templates/django/forms/errors/dict/default.html -> build/lib/django/forms/templates/django/forms/errors/dict copying django/forms/templates/django/forms/errors/dict/text.txt -> build/lib/django/forms/templates/django/forms/errors/dict copying django/forms/templates/django/forms/errors/dict/ul.html -> build/lib/django/forms/templates/django/forms/errors/dict creating build/lib/django/forms/templates/django/forms/errors/list copying django/forms/templates/django/forms/errors/list/default.html -> build/lib/django/forms/templates/django/forms/errors/list copying django/forms/templates/django/forms/errors/list/text.txt -> build/lib/django/forms/templates/django/forms/errors/list copying django/forms/templates/django/forms/errors/list/ul.html -> build/lib/django/forms/templates/django/forms/errors/list creating build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/default.html -> build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/div.html -> build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/p.html -> build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/table.html -> build/lib/django/forms/templates/django/forms/formsets copying django/forms/templates/django/forms/formsets/ul.html -> build/lib/django/forms/templates/django/forms/formsets creating build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/attrs.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/checkbox.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/date.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/datetime.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/email.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/file.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/hidden.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/input.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/input_option.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/multiple_input.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/multiwidget.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/number.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/password.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/radio.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/radio_option.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/select.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/select_date.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/select_option.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/text.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/textarea.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/time.html -> build/lib/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/url.html -> build/lib/django/forms/templates/django/forms/widgets copying django/conf/__init__.py.orig -> build/lib/django/conf creating build/lib/django/conf/app_template copying django/conf/app_template/__init__.py-tpl -> build/lib/django/conf/app_template copying django/conf/app_template/admin.py-tpl -> build/lib/django/conf/app_template copying django/conf/app_template/apps.py-tpl -> build/lib/django/conf/app_template copying django/conf/app_template/models.py-tpl -> build/lib/django/conf/app_template copying django/conf/app_template/tests.py-tpl -> build/lib/django/conf/app_template copying django/conf/app_template/views.py-tpl -> build/lib/django/conf/app_template creating build/lib/django/conf/app_template/migrations copying django/conf/app_template/migrations/__init__.py-tpl -> build/lib/django/conf/app_template/migrations creating build/lib/django/conf/project_template copying django/conf/project_template/manage.py-tpl -> build/lib/django/conf/project_template creating build/lib/django/conf/project_template/project_name copying django/conf/project_template/project_name/__init__.py-tpl -> build/lib/django/conf/project_template/project_name copying django/conf/project_template/project_name/asgi.py-tpl -> build/lib/django/conf/project_template/project_name copying django/conf/project_template/project_name/settings.py-tpl -> build/lib/django/conf/project_template/project_name copying django/conf/project_template/project_name/urls.py-tpl -> build/lib/django/conf/project_template/project_name copying django/conf/project_template/project_name/wsgi.py-tpl -> build/lib/django/conf/project_template/project_name copying django/dispatch/license.txt -> build/lib/django/dispatch creating build/lib/django/contrib/gis/locale creating build/lib/django/contrib/gis/locale/af creating build/lib/django/contrib/gis/locale/af/LC_MESSAGES copying django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES copying django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ar creating build/lib/django/contrib/gis/locale/ar/LC_MESSAGES copying django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES copying django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ar_DZ creating build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ast creating build/lib/django/contrib/gis/locale/ast/LC_MESSAGES copying django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES copying django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES creating build/lib/django/contrib/gis/locale/az creating build/lib/django/contrib/gis/locale/az/LC_MESSAGES copying django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES copying django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES creating build/lib/django/contrib/gis/locale/be creating build/lib/django/contrib/gis/locale/be/LC_MESSAGES copying django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES copying django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES creating build/lib/django/contrib/gis/locale/bg creating build/lib/django/contrib/gis/locale/bg/LC_MESSAGES copying django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES copying django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES creating build/lib/django/contrib/gis/locale/bn creating build/lib/django/contrib/gis/locale/bn/LC_MESSAGES copying django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES copying django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES creating build/lib/django/contrib/gis/locale/br creating build/lib/django/contrib/gis/locale/br/LC_MESSAGES copying django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES copying django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES creating build/lib/django/contrib/gis/locale/bs creating build/lib/django/contrib/gis/locale/bs/LC_MESSAGES copying django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES copying django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ca creating build/lib/django/contrib/gis/locale/ca/LC_MESSAGES copying django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES copying django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ckb creating build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/gis/locale/cs creating build/lib/django/contrib/gis/locale/cs/LC_MESSAGES copying django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES copying django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES creating build/lib/django/contrib/gis/locale/cy creating build/lib/django/contrib/gis/locale/cy/LC_MESSAGES copying django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES copying django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES creating build/lib/django/contrib/gis/locale/da creating build/lib/django/contrib/gis/locale/da/LC_MESSAGES copying django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES copying django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES creating build/lib/django/contrib/gis/locale/de creating build/lib/django/contrib/gis/locale/de/LC_MESSAGES copying django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES copying django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES creating build/lib/django/contrib/gis/locale/dsb creating build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/gis/locale/el creating build/lib/django/contrib/gis/locale/el/LC_MESSAGES copying django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES copying django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES creating build/lib/django/contrib/gis/locale/en creating build/lib/django/contrib/gis/locale/en/LC_MESSAGES copying django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES copying django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES creating build/lib/django/contrib/gis/locale/en_AU creating build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/gis/locale/en_GB creating build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/gis/locale/eo creating build/lib/django/contrib/gis/locale/eo/LC_MESSAGES copying django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES copying django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES creating build/lib/django/contrib/gis/locale/es creating build/lib/django/contrib/gis/locale/es/LC_MESSAGES copying django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES copying django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES creating build/lib/django/contrib/gis/locale/es_AR creating build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/gis/locale/es_CO creating build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/gis/locale/es_MX creating build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/gis/locale/es_VE creating build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/gis/locale/et creating build/lib/django/contrib/gis/locale/et/LC_MESSAGES copying django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES copying django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES creating build/lib/django/contrib/gis/locale/eu creating build/lib/django/contrib/gis/locale/eu/LC_MESSAGES copying django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES copying django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES creating build/lib/django/contrib/gis/locale/fa creating build/lib/django/contrib/gis/locale/fa/LC_MESSAGES copying django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES copying django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES creating build/lib/django/contrib/gis/locale/fi creating build/lib/django/contrib/gis/locale/fi/LC_MESSAGES copying django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES copying django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES creating build/lib/django/contrib/gis/locale/fr creating build/lib/django/contrib/gis/locale/fr/LC_MESSAGES copying django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES copying django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES creating build/lib/django/contrib/gis/locale/fy creating build/lib/django/contrib/gis/locale/fy/LC_MESSAGES copying django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES copying django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ga creating build/lib/django/contrib/gis/locale/ga/LC_MESSAGES copying django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES copying django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES creating build/lib/django/contrib/gis/locale/gd creating build/lib/django/contrib/gis/locale/gd/LC_MESSAGES copying django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES copying django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES creating build/lib/django/contrib/gis/locale/gl creating build/lib/django/contrib/gis/locale/gl/LC_MESSAGES copying django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES copying django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES creating build/lib/django/contrib/gis/locale/he creating build/lib/django/contrib/gis/locale/he/LC_MESSAGES copying django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES copying django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES creating build/lib/django/contrib/gis/locale/hi creating build/lib/django/contrib/gis/locale/hi/LC_MESSAGES copying django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES copying django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES creating build/lib/django/contrib/gis/locale/hr creating build/lib/django/contrib/gis/locale/hr/LC_MESSAGES copying django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES copying django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES creating build/lib/django/contrib/gis/locale/hsb creating build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/gis/locale/hu creating build/lib/django/contrib/gis/locale/hu/LC_MESSAGES copying django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES copying django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES creating build/lib/django/contrib/gis/locale/hy creating build/lib/django/contrib/gis/locale/hy/LC_MESSAGES copying django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES copying django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ia creating build/lib/django/contrib/gis/locale/ia/LC_MESSAGES copying django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES copying django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES creating build/lib/django/contrib/gis/locale/id creating build/lib/django/contrib/gis/locale/id/LC_MESSAGES copying django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES copying django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES creating build/lib/django/contrib/gis/locale/io creating build/lib/django/contrib/gis/locale/io/LC_MESSAGES copying django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES copying django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES creating build/lib/django/contrib/gis/locale/is creating build/lib/django/contrib/gis/locale/is/LC_MESSAGES copying django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES copying django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES creating build/lib/django/contrib/gis/locale/it creating build/lib/django/contrib/gis/locale/it/LC_MESSAGES copying django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES copying django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ja creating build/lib/django/contrib/gis/locale/ja/LC_MESSAGES copying django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES copying django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ka creating build/lib/django/contrib/gis/locale/ka/LC_MESSAGES copying django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES copying django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES creating build/lib/django/contrib/gis/locale/kk creating build/lib/django/contrib/gis/locale/kk/LC_MESSAGES copying django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES copying django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES creating build/lib/django/contrib/gis/locale/km creating build/lib/django/contrib/gis/locale/km/LC_MESSAGES copying django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES copying django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES creating build/lib/django/contrib/gis/locale/kn creating build/lib/django/contrib/gis/locale/kn/LC_MESSAGES copying django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES copying django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ko creating build/lib/django/contrib/gis/locale/ko/LC_MESSAGES copying django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES copying django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ky creating build/lib/django/contrib/gis/locale/ky/LC_MESSAGES copying django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES copying django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES creating build/lib/django/contrib/gis/locale/lb creating build/lib/django/contrib/gis/locale/lb/LC_MESSAGES copying django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES copying django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES creating build/lib/django/contrib/gis/locale/lt creating build/lib/django/contrib/gis/locale/lt/LC_MESSAGES copying django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES copying django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES creating build/lib/django/contrib/gis/locale/lv creating build/lib/django/contrib/gis/locale/lv/LC_MESSAGES copying django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES copying django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES creating build/lib/django/contrib/gis/locale/mk creating build/lib/django/contrib/gis/locale/mk/LC_MESSAGES copying django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES copying django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ml creating build/lib/django/contrib/gis/locale/ml/LC_MESSAGES copying django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES copying django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES creating build/lib/django/contrib/gis/locale/mn creating build/lib/django/contrib/gis/locale/mn/LC_MESSAGES copying django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES copying django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES creating build/lib/django/contrib/gis/locale/mr creating build/lib/django/contrib/gis/locale/mr/LC_MESSAGES copying django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES copying django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ms creating build/lib/django/contrib/gis/locale/ms/LC_MESSAGES copying django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES copying django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES creating build/lib/django/contrib/gis/locale/my creating build/lib/django/contrib/gis/locale/my/LC_MESSAGES copying django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES copying django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES creating build/lib/django/contrib/gis/locale/nb creating build/lib/django/contrib/gis/locale/nb/LC_MESSAGES copying django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES copying django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ne creating build/lib/django/contrib/gis/locale/ne/LC_MESSAGES copying django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES copying django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES creating build/lib/django/contrib/gis/locale/nl creating build/lib/django/contrib/gis/locale/nl/LC_MESSAGES copying django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES copying django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES creating build/lib/django/contrib/gis/locale/nn creating build/lib/django/contrib/gis/locale/nn/LC_MESSAGES copying django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES copying django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES creating build/lib/django/contrib/gis/locale/os creating build/lib/django/contrib/gis/locale/os/LC_MESSAGES copying django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES copying django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES creating build/lib/django/contrib/gis/locale/pa creating build/lib/django/contrib/gis/locale/pa/LC_MESSAGES copying django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES copying django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES creating build/lib/django/contrib/gis/locale/pl creating build/lib/django/contrib/gis/locale/pl/LC_MESSAGES copying django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES copying django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES creating build/lib/django/contrib/gis/locale/pt creating build/lib/django/contrib/gis/locale/pt/LC_MESSAGES copying django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES copying django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES creating build/lib/django/contrib/gis/locale/pt_BR creating build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ro creating build/lib/django/contrib/gis/locale/ro/LC_MESSAGES copying django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES copying django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ru creating build/lib/django/contrib/gis/locale/ru/LC_MESSAGES copying django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES copying django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES creating build/lib/django/contrib/gis/locale/sk creating build/lib/django/contrib/gis/locale/sk/LC_MESSAGES copying django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES copying django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES creating build/lib/django/contrib/gis/locale/sl creating build/lib/django/contrib/gis/locale/sl/LC_MESSAGES copying django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES copying django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES creating build/lib/django/contrib/gis/locale/sq creating build/lib/django/contrib/gis/locale/sq/LC_MESSAGES copying django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES copying django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES creating build/lib/django/contrib/gis/locale/sr creating build/lib/django/contrib/gis/locale/sr/LC_MESSAGES copying django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES copying django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES creating build/lib/django/contrib/gis/locale/sr_Latn creating build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/gis/locale/sv creating build/lib/django/contrib/gis/locale/sv/LC_MESSAGES copying django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES copying django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES creating build/lib/django/contrib/gis/locale/sw creating build/lib/django/contrib/gis/locale/sw/LC_MESSAGES copying django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES copying django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ta creating build/lib/django/contrib/gis/locale/ta/LC_MESSAGES copying django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES copying django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES creating build/lib/django/contrib/gis/locale/te creating build/lib/django/contrib/gis/locale/te/LC_MESSAGES copying django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES copying django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES creating build/lib/django/contrib/gis/locale/tg creating build/lib/django/contrib/gis/locale/tg/LC_MESSAGES copying django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES copying django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES creating build/lib/django/contrib/gis/locale/th creating build/lib/django/contrib/gis/locale/th/LC_MESSAGES copying django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES copying django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES creating build/lib/django/contrib/gis/locale/tr creating build/lib/django/contrib/gis/locale/tr/LC_MESSAGES copying django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES copying django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES creating build/lib/django/contrib/gis/locale/tt creating build/lib/django/contrib/gis/locale/tt/LC_MESSAGES copying django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES copying django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES creating build/lib/django/contrib/gis/locale/udm creating build/lib/django/contrib/gis/locale/udm/LC_MESSAGES copying django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES copying django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES creating build/lib/django/contrib/gis/locale/uk creating build/lib/django/contrib/gis/locale/uk/LC_MESSAGES copying django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES copying django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES creating build/lib/django/contrib/gis/locale/ur creating build/lib/django/contrib/gis/locale/ur/LC_MESSAGES copying django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES copying django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES creating build/lib/django/contrib/gis/locale/vi creating build/lib/django/contrib/gis/locale/vi/LC_MESSAGES copying django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES copying django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES creating build/lib/django/contrib/gis/locale/zh_Hans creating build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/gis/locale/zh_Hant creating build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/gis/static creating build/lib/django/contrib/gis/static/gis creating build/lib/django/contrib/gis/static/gis/css copying django/contrib/gis/static/gis/css/ol3.css -> build/lib/django/contrib/gis/static/gis/css creating build/lib/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_line_off.svg -> build/lib/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_line_on.svg -> build/lib/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_point_off.svg -> build/lib/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_point_on.svg -> build/lib/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/lib/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/lib/django/contrib/gis/static/gis/img creating build/lib/django/contrib/gis/static/gis/js copying django/contrib/gis/static/gis/js/OLMapWidget.js -> build/lib/django/contrib/gis/static/gis/js creating build/lib/django/contrib/gis/templates creating build/lib/django/contrib/gis/templates/gis copying django/contrib/gis/templates/gis/openlayers-osm.html -> build/lib/django/contrib/gis/templates/gis copying django/contrib/gis/templates/gis/openlayers.html -> build/lib/django/contrib/gis/templates/gis creating build/lib/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/openlayers.html -> build/lib/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/openlayers.js -> build/lib/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/osm.html -> build/lib/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/osm.js -> build/lib/django/contrib/gis/templates/gis/admin creating build/lib/django/contrib/gis/templates/gis/kml copying django/contrib/gis/templates/gis/kml/base.kml -> build/lib/django/contrib/gis/templates/gis/kml copying django/contrib/gis/templates/gis/kml/placemarks.kml -> build/lib/django/contrib/gis/templates/gis/kml creating build/lib/django/contrib/flatpages/locale creating build/lib/django/contrib/flatpages/locale/af creating build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ar creating build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ar_DZ creating build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ast creating build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/az creating build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/be creating build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/bg creating build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/bn creating build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/br creating build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/bs creating build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ca creating build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ckb creating build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/cs creating build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/cy creating build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/da creating build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/de creating build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/dsb creating build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/el creating build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/en creating build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/en_AU creating build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/en_GB creating build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/eo creating build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/es creating build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/es_AR creating build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/es_CO creating build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/es_MX creating build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/es_VE creating build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/et creating build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/eu creating build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/fa creating build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/fi creating build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/fr creating build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/fy creating build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ga creating build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/gd creating build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/gl creating build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/he creating build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/hi creating build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/hr creating build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/hsb creating build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/hu creating build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/hy creating build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ia creating build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/id creating build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/io creating build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/is creating build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/it creating build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ja creating build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ka creating build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/kk creating build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/km creating build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/kn creating build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ko creating build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ky creating build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/lb creating build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/lt creating build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/lv creating build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/mk creating build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ml creating build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/mn creating build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/mr creating build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ms creating build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/my creating build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/nb creating build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ne creating build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/nl creating build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/nn creating build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/os creating build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/pa creating build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/pl creating build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/pt creating build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/pt_BR creating build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ro creating build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ru creating build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/sk creating build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/sl creating build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/sq creating build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/sr creating build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/sr_Latn creating build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/sv creating build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/sw creating build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ta creating build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/te creating build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/tg creating build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/th creating build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/tk creating build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/tr creating build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/tt creating build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/udm creating build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/uk creating build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/ur creating build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/vi creating build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/zh_Hans creating build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/flatpages/locale/zh_Hant creating build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/sites/locale creating build/lib/django/contrib/sites/locale/af creating build/lib/django/contrib/sites/locale/af/LC_MESSAGES copying django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES copying django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ar creating build/lib/django/contrib/sites/locale/ar/LC_MESSAGES copying django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES copying django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ar_DZ creating build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ast creating build/lib/django/contrib/sites/locale/ast/LC_MESSAGES copying django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES copying django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES creating build/lib/django/contrib/sites/locale/az creating build/lib/django/contrib/sites/locale/az/LC_MESSAGES copying django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES copying django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES creating build/lib/django/contrib/sites/locale/be creating build/lib/django/contrib/sites/locale/be/LC_MESSAGES copying django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES copying django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES creating build/lib/django/contrib/sites/locale/bg creating build/lib/django/contrib/sites/locale/bg/LC_MESSAGES copying django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES copying django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES creating build/lib/django/contrib/sites/locale/bn creating build/lib/django/contrib/sites/locale/bn/LC_MESSAGES copying django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES copying django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES creating build/lib/django/contrib/sites/locale/br creating build/lib/django/contrib/sites/locale/br/LC_MESSAGES copying django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES copying django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES creating build/lib/django/contrib/sites/locale/bs creating build/lib/django/contrib/sites/locale/bs/LC_MESSAGES copying django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES copying django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ca creating build/lib/django/contrib/sites/locale/ca/LC_MESSAGES copying django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES copying django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ckb creating build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/sites/locale/cs creating build/lib/django/contrib/sites/locale/cs/LC_MESSAGES copying django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES copying django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES creating build/lib/django/contrib/sites/locale/cy creating build/lib/django/contrib/sites/locale/cy/LC_MESSAGES copying django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES copying django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES creating build/lib/django/contrib/sites/locale/da creating build/lib/django/contrib/sites/locale/da/LC_MESSAGES copying django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES copying django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES creating build/lib/django/contrib/sites/locale/de creating build/lib/django/contrib/sites/locale/de/LC_MESSAGES copying django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES copying django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES creating build/lib/django/contrib/sites/locale/dsb creating build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/sites/locale/el creating build/lib/django/contrib/sites/locale/el/LC_MESSAGES copying django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES copying django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES creating build/lib/django/contrib/sites/locale/en creating build/lib/django/contrib/sites/locale/en/LC_MESSAGES copying django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES copying django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES creating build/lib/django/contrib/sites/locale/en_AU creating build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/sites/locale/en_GB creating build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/sites/locale/eo creating build/lib/django/contrib/sites/locale/eo/LC_MESSAGES copying django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES copying django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES creating build/lib/django/contrib/sites/locale/es creating build/lib/django/contrib/sites/locale/es/LC_MESSAGES copying django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES copying django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES creating build/lib/django/contrib/sites/locale/es_AR creating build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/sites/locale/es_CO creating build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/sites/locale/es_MX creating build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/sites/locale/es_VE creating build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/sites/locale/et creating build/lib/django/contrib/sites/locale/et/LC_MESSAGES copying django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES copying django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES creating build/lib/django/contrib/sites/locale/eu creating build/lib/django/contrib/sites/locale/eu/LC_MESSAGES copying django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES copying django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES creating build/lib/django/contrib/sites/locale/fa creating build/lib/django/contrib/sites/locale/fa/LC_MESSAGES copying django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES copying django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES creating build/lib/django/contrib/sites/locale/fi creating build/lib/django/contrib/sites/locale/fi/LC_MESSAGES copying django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES copying django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES creating build/lib/django/contrib/sites/locale/fr creating build/lib/django/contrib/sites/locale/fr/LC_MESSAGES copying django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES copying django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES creating build/lib/django/contrib/sites/locale/fy creating build/lib/django/contrib/sites/locale/fy/LC_MESSAGES copying django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES copying django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ga creating build/lib/django/contrib/sites/locale/ga/LC_MESSAGES copying django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES copying django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES creating build/lib/django/contrib/sites/locale/gd creating build/lib/django/contrib/sites/locale/gd/LC_MESSAGES copying django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES copying django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES creating build/lib/django/contrib/sites/locale/gl creating build/lib/django/contrib/sites/locale/gl/LC_MESSAGES copying django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES copying django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES creating build/lib/django/contrib/sites/locale/he creating build/lib/django/contrib/sites/locale/he/LC_MESSAGES copying django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES copying django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES creating build/lib/django/contrib/sites/locale/hi creating build/lib/django/contrib/sites/locale/hi/LC_MESSAGES copying django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES copying django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES creating build/lib/django/contrib/sites/locale/hr creating build/lib/django/contrib/sites/locale/hr/LC_MESSAGES copying django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES copying django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES creating build/lib/django/contrib/sites/locale/hsb creating build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/sites/locale/hu creating build/lib/django/contrib/sites/locale/hu/LC_MESSAGES copying django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES copying django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES creating build/lib/django/contrib/sites/locale/hy creating build/lib/django/contrib/sites/locale/hy/LC_MESSAGES copying django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES copying django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ia creating build/lib/django/contrib/sites/locale/ia/LC_MESSAGES copying django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES copying django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES creating build/lib/django/contrib/sites/locale/id creating build/lib/django/contrib/sites/locale/id/LC_MESSAGES copying django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES copying django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES creating build/lib/django/contrib/sites/locale/io creating build/lib/django/contrib/sites/locale/io/LC_MESSAGES copying django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES copying django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES creating build/lib/django/contrib/sites/locale/is creating build/lib/django/contrib/sites/locale/is/LC_MESSAGES copying django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES copying django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES creating build/lib/django/contrib/sites/locale/it creating build/lib/django/contrib/sites/locale/it/LC_MESSAGES copying django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES copying django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ja creating build/lib/django/contrib/sites/locale/ja/LC_MESSAGES copying django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES copying django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ka creating build/lib/django/contrib/sites/locale/ka/LC_MESSAGES copying django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES copying django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES creating build/lib/django/contrib/sites/locale/kab creating build/lib/django/contrib/sites/locale/kab/LC_MESSAGES copying django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES copying django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES creating build/lib/django/contrib/sites/locale/kk creating build/lib/django/contrib/sites/locale/kk/LC_MESSAGES copying django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES copying django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES creating build/lib/django/contrib/sites/locale/km creating build/lib/django/contrib/sites/locale/km/LC_MESSAGES copying django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES copying django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES creating build/lib/django/contrib/sites/locale/kn creating build/lib/django/contrib/sites/locale/kn/LC_MESSAGES copying django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES copying django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ko creating build/lib/django/contrib/sites/locale/ko/LC_MESSAGES copying django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES copying django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ky creating build/lib/django/contrib/sites/locale/ky/LC_MESSAGES copying django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES copying django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES creating build/lib/django/contrib/sites/locale/lb creating build/lib/django/contrib/sites/locale/lb/LC_MESSAGES copying django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES copying django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES creating build/lib/django/contrib/sites/locale/lt creating build/lib/django/contrib/sites/locale/lt/LC_MESSAGES copying django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES copying django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES creating build/lib/django/contrib/sites/locale/lv creating build/lib/django/contrib/sites/locale/lv/LC_MESSAGES copying django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES copying django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES creating build/lib/django/contrib/sites/locale/mk creating build/lib/django/contrib/sites/locale/mk/LC_MESSAGES copying django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES copying django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ml creating build/lib/django/contrib/sites/locale/ml/LC_MESSAGES copying django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES copying django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES creating build/lib/django/contrib/sites/locale/mn creating build/lib/django/contrib/sites/locale/mn/LC_MESSAGES copying django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES copying django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES creating build/lib/django/contrib/sites/locale/mr creating build/lib/django/contrib/sites/locale/mr/LC_MESSAGES copying django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES copying django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ms creating build/lib/django/contrib/sites/locale/ms/LC_MESSAGES copying django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES copying django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES creating build/lib/django/contrib/sites/locale/my creating build/lib/django/contrib/sites/locale/my/LC_MESSAGES copying django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES copying django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES creating build/lib/django/contrib/sites/locale/nb creating build/lib/django/contrib/sites/locale/nb/LC_MESSAGES copying django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES copying django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ne creating build/lib/django/contrib/sites/locale/ne/LC_MESSAGES copying django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES copying django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES creating build/lib/django/contrib/sites/locale/nl creating build/lib/django/contrib/sites/locale/nl/LC_MESSAGES copying django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES copying django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES creating build/lib/django/contrib/sites/locale/nn creating build/lib/django/contrib/sites/locale/nn/LC_MESSAGES copying django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES copying django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES creating build/lib/django/contrib/sites/locale/os creating build/lib/django/contrib/sites/locale/os/LC_MESSAGES copying django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES copying django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES creating build/lib/django/contrib/sites/locale/pa creating build/lib/django/contrib/sites/locale/pa/LC_MESSAGES copying django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES copying django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES creating build/lib/django/contrib/sites/locale/pl creating build/lib/django/contrib/sites/locale/pl/LC_MESSAGES copying django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES copying django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES creating build/lib/django/contrib/sites/locale/pt creating build/lib/django/contrib/sites/locale/pt/LC_MESSAGES copying django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES copying django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES creating build/lib/django/contrib/sites/locale/pt_BR creating build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ro creating build/lib/django/contrib/sites/locale/ro/LC_MESSAGES copying django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES copying django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ru creating build/lib/django/contrib/sites/locale/ru/LC_MESSAGES copying django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES copying django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES creating build/lib/django/contrib/sites/locale/sk creating build/lib/django/contrib/sites/locale/sk/LC_MESSAGES copying django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES copying django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES creating build/lib/django/contrib/sites/locale/sl creating build/lib/django/contrib/sites/locale/sl/LC_MESSAGES copying django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES copying django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES creating build/lib/django/contrib/sites/locale/sq creating build/lib/django/contrib/sites/locale/sq/LC_MESSAGES copying django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES copying django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES creating build/lib/django/contrib/sites/locale/sr creating build/lib/django/contrib/sites/locale/sr/LC_MESSAGES copying django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES copying django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES creating build/lib/django/contrib/sites/locale/sr_Latn creating build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/sites/locale/sv creating build/lib/django/contrib/sites/locale/sv/LC_MESSAGES copying django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES copying django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES creating build/lib/django/contrib/sites/locale/sw creating build/lib/django/contrib/sites/locale/sw/LC_MESSAGES copying django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES copying django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ta creating build/lib/django/contrib/sites/locale/ta/LC_MESSAGES copying django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES copying django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES creating build/lib/django/contrib/sites/locale/te creating build/lib/django/contrib/sites/locale/te/LC_MESSAGES copying django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES copying django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES creating build/lib/django/contrib/sites/locale/tg creating build/lib/django/contrib/sites/locale/tg/LC_MESSAGES copying django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES copying django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES creating build/lib/django/contrib/sites/locale/th creating build/lib/django/contrib/sites/locale/th/LC_MESSAGES copying django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES copying django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES creating build/lib/django/contrib/sites/locale/tk creating build/lib/django/contrib/sites/locale/tk/LC_MESSAGES copying django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES copying django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES creating build/lib/django/contrib/sites/locale/tr creating build/lib/django/contrib/sites/locale/tr/LC_MESSAGES copying django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES copying django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES creating build/lib/django/contrib/sites/locale/tt creating build/lib/django/contrib/sites/locale/tt/LC_MESSAGES copying django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES copying django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES creating build/lib/django/contrib/sites/locale/udm creating build/lib/django/contrib/sites/locale/udm/LC_MESSAGES copying django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES copying django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES creating build/lib/django/contrib/sites/locale/uk creating build/lib/django/contrib/sites/locale/uk/LC_MESSAGES copying django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES copying django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES creating build/lib/django/contrib/sites/locale/ur creating build/lib/django/contrib/sites/locale/ur/LC_MESSAGES copying django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES copying django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES creating build/lib/django/contrib/sites/locale/uz creating build/lib/django/contrib/sites/locale/uz/LC_MESSAGES copying django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES copying django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES creating build/lib/django/contrib/sites/locale/vi creating build/lib/django/contrib/sites/locale/vi/LC_MESSAGES copying django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES copying django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES creating build/lib/django/contrib/sites/locale/zh_Hans creating build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/sites/locale/zh_Hant creating build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/sitemaps/templates copying django/contrib/sitemaps/templates/sitemap.xml -> build/lib/django/contrib/sitemaps/templates copying django/contrib/sitemaps/templates/sitemap_index.xml -> build/lib/django/contrib/sitemaps/templates copying django/contrib/auth/common-passwords.txt.gz -> build/lib/django/contrib/auth creating build/lib/django/contrib/auth/locale creating build/lib/django/contrib/auth/locale/af creating build/lib/django/contrib/auth/locale/af/LC_MESSAGES copying django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES copying django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ar creating build/lib/django/contrib/auth/locale/ar/LC_MESSAGES copying django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES copying django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ar_DZ creating build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ast creating build/lib/django/contrib/auth/locale/ast/LC_MESSAGES copying django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES copying django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES creating build/lib/django/contrib/auth/locale/az creating build/lib/django/contrib/auth/locale/az/LC_MESSAGES copying django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES copying django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES creating build/lib/django/contrib/auth/locale/be creating build/lib/django/contrib/auth/locale/be/LC_MESSAGES copying django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES copying django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES creating build/lib/django/contrib/auth/locale/bg creating build/lib/django/contrib/auth/locale/bg/LC_MESSAGES copying django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES copying django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES creating build/lib/django/contrib/auth/locale/bn creating build/lib/django/contrib/auth/locale/bn/LC_MESSAGES copying django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES copying django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES creating build/lib/django/contrib/auth/locale/br creating build/lib/django/contrib/auth/locale/br/LC_MESSAGES copying django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES copying django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES creating build/lib/django/contrib/auth/locale/bs creating build/lib/django/contrib/auth/locale/bs/LC_MESSAGES copying django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES copying django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ca creating build/lib/django/contrib/auth/locale/ca/LC_MESSAGES copying django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES copying django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ckb creating build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/auth/locale/cs creating build/lib/django/contrib/auth/locale/cs/LC_MESSAGES copying django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES copying django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES creating build/lib/django/contrib/auth/locale/cy creating build/lib/django/contrib/auth/locale/cy/LC_MESSAGES copying django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES copying django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES creating build/lib/django/contrib/auth/locale/da creating build/lib/django/contrib/auth/locale/da/LC_MESSAGES copying django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES copying django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES creating build/lib/django/contrib/auth/locale/de creating build/lib/django/contrib/auth/locale/de/LC_MESSAGES copying django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES copying django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES creating build/lib/django/contrib/auth/locale/dsb creating build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/auth/locale/el creating build/lib/django/contrib/auth/locale/el/LC_MESSAGES copying django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES copying django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES creating build/lib/django/contrib/auth/locale/en creating build/lib/django/contrib/auth/locale/en/LC_MESSAGES copying django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES copying django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES creating build/lib/django/contrib/auth/locale/en_AU creating build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/auth/locale/en_GB creating build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/auth/locale/eo creating build/lib/django/contrib/auth/locale/eo/LC_MESSAGES copying django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES copying django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES creating build/lib/django/contrib/auth/locale/es creating build/lib/django/contrib/auth/locale/es/LC_MESSAGES copying django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES copying django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES creating build/lib/django/contrib/auth/locale/es_AR creating build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/auth/locale/es_CO creating build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/auth/locale/es_MX creating build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/auth/locale/es_VE creating build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/auth/locale/et creating build/lib/django/contrib/auth/locale/et/LC_MESSAGES copying django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES copying django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES creating build/lib/django/contrib/auth/locale/eu creating build/lib/django/contrib/auth/locale/eu/LC_MESSAGES copying django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES copying django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES creating build/lib/django/contrib/auth/locale/fa creating build/lib/django/contrib/auth/locale/fa/LC_MESSAGES copying django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES copying django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES creating build/lib/django/contrib/auth/locale/fi creating build/lib/django/contrib/auth/locale/fi/LC_MESSAGES copying django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES copying django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES creating build/lib/django/contrib/auth/locale/fr creating build/lib/django/contrib/auth/locale/fr/LC_MESSAGES copying django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES copying django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES creating build/lib/django/contrib/auth/locale/fy creating build/lib/django/contrib/auth/locale/fy/LC_MESSAGES copying django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES copying django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ga creating build/lib/django/contrib/auth/locale/ga/LC_MESSAGES copying django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES copying django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES creating build/lib/django/contrib/auth/locale/gd creating build/lib/django/contrib/auth/locale/gd/LC_MESSAGES copying django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES copying django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES creating build/lib/django/contrib/auth/locale/gl creating build/lib/django/contrib/auth/locale/gl/LC_MESSAGES copying django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES copying django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES creating build/lib/django/contrib/auth/locale/he creating build/lib/django/contrib/auth/locale/he/LC_MESSAGES copying django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES copying django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES creating build/lib/django/contrib/auth/locale/hi creating build/lib/django/contrib/auth/locale/hi/LC_MESSAGES copying django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES copying django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES creating build/lib/django/contrib/auth/locale/hr creating build/lib/django/contrib/auth/locale/hr/LC_MESSAGES copying django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES copying django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES creating build/lib/django/contrib/auth/locale/hsb creating build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/auth/locale/hu creating build/lib/django/contrib/auth/locale/hu/LC_MESSAGES copying django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES copying django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES creating build/lib/django/contrib/auth/locale/hy creating build/lib/django/contrib/auth/locale/hy/LC_MESSAGES copying django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES copying django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ia creating build/lib/django/contrib/auth/locale/ia/LC_MESSAGES copying django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES copying django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES creating build/lib/django/contrib/auth/locale/id creating build/lib/django/contrib/auth/locale/id/LC_MESSAGES copying django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES copying django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES creating build/lib/django/contrib/auth/locale/io creating build/lib/django/contrib/auth/locale/io/LC_MESSAGES copying django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES copying django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES creating build/lib/django/contrib/auth/locale/is creating build/lib/django/contrib/auth/locale/is/LC_MESSAGES copying django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES copying django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES creating build/lib/django/contrib/auth/locale/it creating build/lib/django/contrib/auth/locale/it/LC_MESSAGES copying django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES copying django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ja creating build/lib/django/contrib/auth/locale/ja/LC_MESSAGES copying django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES copying django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ka creating build/lib/django/contrib/auth/locale/ka/LC_MESSAGES copying django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES copying django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES creating build/lib/django/contrib/auth/locale/kab creating build/lib/django/contrib/auth/locale/kab/LC_MESSAGES copying django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES copying django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES creating build/lib/django/contrib/auth/locale/kk creating build/lib/django/contrib/auth/locale/kk/LC_MESSAGES copying django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES copying django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES creating build/lib/django/contrib/auth/locale/km creating build/lib/django/contrib/auth/locale/km/LC_MESSAGES copying django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES copying django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES creating build/lib/django/contrib/auth/locale/kn creating build/lib/django/contrib/auth/locale/kn/LC_MESSAGES copying django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES copying django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ko creating build/lib/django/contrib/auth/locale/ko/LC_MESSAGES copying django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES copying django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ky creating build/lib/django/contrib/auth/locale/ky/LC_MESSAGES copying django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES copying django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES creating build/lib/django/contrib/auth/locale/lb creating build/lib/django/contrib/auth/locale/lb/LC_MESSAGES copying django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES copying django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES creating build/lib/django/contrib/auth/locale/lt creating build/lib/django/contrib/auth/locale/lt/LC_MESSAGES copying django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES copying django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES creating build/lib/django/contrib/auth/locale/lv creating build/lib/django/contrib/auth/locale/lv/LC_MESSAGES copying django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES copying django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES creating build/lib/django/contrib/auth/locale/mk creating build/lib/django/contrib/auth/locale/mk/LC_MESSAGES copying django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES copying django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ml creating build/lib/django/contrib/auth/locale/ml/LC_MESSAGES copying django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES copying django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES creating build/lib/django/contrib/auth/locale/mn creating build/lib/django/contrib/auth/locale/mn/LC_MESSAGES copying django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES copying django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES creating build/lib/django/contrib/auth/locale/mr creating build/lib/django/contrib/auth/locale/mr/LC_MESSAGES copying django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES copying django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ms creating build/lib/django/contrib/auth/locale/ms/LC_MESSAGES copying django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES copying django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES creating build/lib/django/contrib/auth/locale/my creating build/lib/django/contrib/auth/locale/my/LC_MESSAGES copying django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES copying django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES creating build/lib/django/contrib/auth/locale/nb creating build/lib/django/contrib/auth/locale/nb/LC_MESSAGES copying django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES copying django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ne creating build/lib/django/contrib/auth/locale/ne/LC_MESSAGES copying django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES copying django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES creating build/lib/django/contrib/auth/locale/nl creating build/lib/django/contrib/auth/locale/nl/LC_MESSAGES copying django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES copying django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES creating build/lib/django/contrib/auth/locale/nn creating build/lib/django/contrib/auth/locale/nn/LC_MESSAGES copying django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES copying django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES creating build/lib/django/contrib/auth/locale/os creating build/lib/django/contrib/auth/locale/os/LC_MESSAGES copying django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES copying django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES creating build/lib/django/contrib/auth/locale/pa creating build/lib/django/contrib/auth/locale/pa/LC_MESSAGES copying django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES copying django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES creating build/lib/django/contrib/auth/locale/pl creating build/lib/django/contrib/auth/locale/pl/LC_MESSAGES copying django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES copying django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES creating build/lib/django/contrib/auth/locale/pt creating build/lib/django/contrib/auth/locale/pt/LC_MESSAGES copying django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES copying django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES creating build/lib/django/contrib/auth/locale/pt_BR creating build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ro creating build/lib/django/contrib/auth/locale/ro/LC_MESSAGES copying django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES copying django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ru creating build/lib/django/contrib/auth/locale/ru/LC_MESSAGES copying django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES copying django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES creating build/lib/django/contrib/auth/locale/sk creating build/lib/django/contrib/auth/locale/sk/LC_MESSAGES copying django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES copying django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES creating build/lib/django/contrib/auth/locale/sl creating build/lib/django/contrib/auth/locale/sl/LC_MESSAGES copying django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES copying django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES creating build/lib/django/contrib/auth/locale/sq creating build/lib/django/contrib/auth/locale/sq/LC_MESSAGES copying django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES copying django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES creating build/lib/django/contrib/auth/locale/sr creating build/lib/django/contrib/auth/locale/sr/LC_MESSAGES copying django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES copying django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES creating build/lib/django/contrib/auth/locale/sr_Latn creating build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/auth/locale/sv creating build/lib/django/contrib/auth/locale/sv/LC_MESSAGES copying django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES copying django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES creating build/lib/django/contrib/auth/locale/sw creating build/lib/django/contrib/auth/locale/sw/LC_MESSAGES copying django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES copying django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ta creating build/lib/django/contrib/auth/locale/ta/LC_MESSAGES copying django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES copying django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES creating build/lib/django/contrib/auth/locale/te creating build/lib/django/contrib/auth/locale/te/LC_MESSAGES copying django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES copying django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES creating build/lib/django/contrib/auth/locale/tg creating build/lib/django/contrib/auth/locale/tg/LC_MESSAGES copying django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES copying django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES creating build/lib/django/contrib/auth/locale/th creating build/lib/django/contrib/auth/locale/th/LC_MESSAGES copying django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES copying django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES creating build/lib/django/contrib/auth/locale/tk creating build/lib/django/contrib/auth/locale/tk/LC_MESSAGES copying django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES copying django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES creating build/lib/django/contrib/auth/locale/tr creating build/lib/django/contrib/auth/locale/tr/LC_MESSAGES copying django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES copying django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES creating build/lib/django/contrib/auth/locale/tt creating build/lib/django/contrib/auth/locale/tt/LC_MESSAGES copying django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES copying django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES creating build/lib/django/contrib/auth/locale/udm creating build/lib/django/contrib/auth/locale/udm/LC_MESSAGES copying django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES copying django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES creating build/lib/django/contrib/auth/locale/uk creating build/lib/django/contrib/auth/locale/uk/LC_MESSAGES copying django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES copying django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES creating build/lib/django/contrib/auth/locale/ur creating build/lib/django/contrib/auth/locale/ur/LC_MESSAGES copying django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES copying django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES creating build/lib/django/contrib/auth/locale/uz creating build/lib/django/contrib/auth/locale/uz/LC_MESSAGES copying django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES copying django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES creating build/lib/django/contrib/auth/locale/vi creating build/lib/django/contrib/auth/locale/vi/LC_MESSAGES copying django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES copying django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES creating build/lib/django/contrib/auth/locale/zh_Hans creating build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/auth/locale/zh_Hant creating build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/auth/templates creating build/lib/django/contrib/auth/templates/auth creating build/lib/django/contrib/auth/templates/auth/widgets copying django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/lib/django/contrib/auth/templates/auth/widgets creating build/lib/django/contrib/auth/templates/registration copying django/contrib/auth/templates/registration/password_reset_subject.txt -> build/lib/django/contrib/auth/templates/registration creating build/lib/django/contrib/redirects/locale creating build/lib/django/contrib/redirects/locale/af creating build/lib/django/contrib/redirects/locale/af/LC_MESSAGES copying django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES copying django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ar creating build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ar_DZ creating build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ast creating build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/az creating build/lib/django/contrib/redirects/locale/az/LC_MESSAGES copying django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES copying django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/be creating build/lib/django/contrib/redirects/locale/be/LC_MESSAGES copying django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES copying django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/bg creating build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/bn creating build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/br creating build/lib/django/contrib/redirects/locale/br/LC_MESSAGES copying django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES copying django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/bs creating build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ca creating build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ckb creating build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/cs creating build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/cy creating build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/da creating build/lib/django/contrib/redirects/locale/da/LC_MESSAGES copying django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES copying django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/de creating build/lib/django/contrib/redirects/locale/de/LC_MESSAGES copying django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES copying django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/dsb creating build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/el creating build/lib/django/contrib/redirects/locale/el/LC_MESSAGES copying django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES copying django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/en creating build/lib/django/contrib/redirects/locale/en/LC_MESSAGES copying django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES copying django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/en_AU creating build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/en_GB creating build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/eo creating build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/es creating build/lib/django/contrib/redirects/locale/es/LC_MESSAGES copying django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES copying django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/es_AR creating build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/es_CO creating build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/es_MX creating build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/es_VE creating build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/et creating build/lib/django/contrib/redirects/locale/et/LC_MESSAGES copying django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES copying django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/eu creating build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/fa creating build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/fi creating build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/fr creating build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/fy creating build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ga creating build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/gd creating build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/gl creating build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/he creating build/lib/django/contrib/redirects/locale/he/LC_MESSAGES copying django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES copying django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/hi creating build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/hr creating build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/hsb creating build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/hu creating build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/hy creating build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ia creating build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/id creating build/lib/django/contrib/redirects/locale/id/LC_MESSAGES copying django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES copying django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/io creating build/lib/django/contrib/redirects/locale/io/LC_MESSAGES copying django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES copying django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/is creating build/lib/django/contrib/redirects/locale/is/LC_MESSAGES copying django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES copying django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/it creating build/lib/django/contrib/redirects/locale/it/LC_MESSAGES copying django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES copying django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ja creating build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ka creating build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/kab creating build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/kk creating build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/km creating build/lib/django/contrib/redirects/locale/km/LC_MESSAGES copying django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES copying django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/kn creating build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ko creating build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ky creating build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/lb creating build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/lt creating build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/lv creating build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/mk creating build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ml creating build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/mn creating build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/mr creating build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ms creating build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/my creating build/lib/django/contrib/redirects/locale/my/LC_MESSAGES copying django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES copying django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/nb creating build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ne creating build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/nl creating build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/nn creating build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/os creating build/lib/django/contrib/redirects/locale/os/LC_MESSAGES copying django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES copying django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/pa creating build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/pl creating build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/pt creating build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/pt_BR creating build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ro creating build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ru creating build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/sk creating build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/sl creating build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/sq creating build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/sr creating build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/sr_Latn creating build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/sv creating build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/sw creating build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ta creating build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/te creating build/lib/django/contrib/redirects/locale/te/LC_MESSAGES copying django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES copying django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/tg creating build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/th creating build/lib/django/contrib/redirects/locale/th/LC_MESSAGES copying django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES copying django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/tk creating build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/tr creating build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/tt creating build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/udm creating build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/uk creating build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/ur creating build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/uz creating build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/vi creating build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/zh_Hans creating build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/redirects/locale/zh_Hant creating build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/humanize/locale creating build/lib/django/contrib/humanize/locale/af creating build/lib/django/contrib/humanize/locale/af/LC_MESSAGES copying django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES copying django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ar creating build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ar_DZ creating build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ast creating build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/az creating build/lib/django/contrib/humanize/locale/az/LC_MESSAGES copying django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES copying django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/be creating build/lib/django/contrib/humanize/locale/be/LC_MESSAGES copying django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES copying django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/bg creating build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/bn creating build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/br creating build/lib/django/contrib/humanize/locale/br/LC_MESSAGES copying django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES copying django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/bs creating build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ca creating build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ckb creating build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/cs creating build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/cy creating build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/da creating build/lib/django/contrib/humanize/locale/da/LC_MESSAGES copying django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES copying django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/de creating build/lib/django/contrib/humanize/locale/de/LC_MESSAGES copying django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES copying django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/dsb creating build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/el creating build/lib/django/contrib/humanize/locale/el/LC_MESSAGES copying django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES copying django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/en creating build/lib/django/contrib/humanize/locale/en/LC_MESSAGES copying django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES copying django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/en_AU creating build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/en_GB creating build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/eo creating build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/es creating build/lib/django/contrib/humanize/locale/es/LC_MESSAGES copying django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES copying django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/es_AR creating build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/es_CO creating build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/es_MX creating build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/es_VE creating build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/et creating build/lib/django/contrib/humanize/locale/et/LC_MESSAGES copying django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES copying django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/eu creating build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/fa creating build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/fi creating build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/fr creating build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/fy creating build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ga creating build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/gd creating build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/gl creating build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/he creating build/lib/django/contrib/humanize/locale/he/LC_MESSAGES copying django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES copying django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/hi creating build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/hr creating build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/hsb creating build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/hu creating build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/hy creating build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ia creating build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/id creating build/lib/django/contrib/humanize/locale/id/LC_MESSAGES copying django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES copying django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/io creating build/lib/django/contrib/humanize/locale/io/LC_MESSAGES copying django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES copying django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/is creating build/lib/django/contrib/humanize/locale/is/LC_MESSAGES copying django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES copying django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/it creating build/lib/django/contrib/humanize/locale/it/LC_MESSAGES copying django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES copying django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ja creating build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ka creating build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/kk creating build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/km creating build/lib/django/contrib/humanize/locale/km/LC_MESSAGES copying django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES copying django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/kn creating build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ko creating build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ky creating build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/lb creating build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/lt creating build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/lv creating build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/mk creating build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ml creating build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/mn creating build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/mr creating build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ms creating build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/my creating build/lib/django/contrib/humanize/locale/my/LC_MESSAGES copying django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES copying django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/nb creating build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ne creating build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/nl creating build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/nn creating build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/os creating build/lib/django/contrib/humanize/locale/os/LC_MESSAGES copying django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES copying django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/pa creating build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/pl creating build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/pt creating build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/pt_BR creating build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ro creating build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ru creating build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/sk creating build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/sl creating build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/sq creating build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/sr creating build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/sr_Latn creating build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/sv creating build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/sw creating build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ta creating build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/te creating build/lib/django/contrib/humanize/locale/te/LC_MESSAGES copying django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES copying django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/tg creating build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/th creating build/lib/django/contrib/humanize/locale/th/LC_MESSAGES copying django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES copying django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/tk creating build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/tr creating build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/tt creating build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/udm creating build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/uk creating build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/ur creating build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/uz creating build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/vi creating build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/zh_Hans creating build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/humanize/locale/zh_Hant creating build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale creating build/lib/django/contrib/contenttypes/locale/af creating build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ar creating build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ar_DZ creating build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ast creating build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/az creating build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/be creating build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/bg creating build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/bn creating build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/br creating build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/bs creating build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ca creating build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ckb creating build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/cs creating build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/cy creating build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/da creating build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/de creating build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/dsb creating build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/el creating build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/en creating build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/en_AU creating build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/en_GB creating build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/eo creating build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/es creating build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/es_AR creating build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/es_CO creating build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/es_MX creating build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/es_VE creating build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/et creating build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/eu creating build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/fa creating build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/fi creating build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/fr creating build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/fy creating build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ga creating build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/gd creating build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/gl creating build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/he creating build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/hi creating build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/hr creating build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/hsb creating build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/hu creating build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/hy creating build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ia creating build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/id creating build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/io creating build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/is creating build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/it creating build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ja creating build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ka creating build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/kk creating build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/km creating build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/kn creating build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ko creating build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ky creating build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/lb creating build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/lt creating build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/lv creating build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/mk creating build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ml creating build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/mn creating build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/mr creating build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ms creating build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/my creating build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/nb creating build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ne creating build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/nl creating build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/nn creating build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/os creating build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/pa creating build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/pl creating build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/pt creating build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/pt_BR creating build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ro creating build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ru creating build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/sk creating build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/sl creating build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/sq creating build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/sr creating build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/sr_Latn creating build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/sv creating build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/sw creating build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ta creating build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/te creating build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/tg creating build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/th creating build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/tk creating build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/tr creating build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/tt creating build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/udm creating build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/uk creating build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/ur creating build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/vi creating build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/zh_Hans creating build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/contenttypes/locale/zh_Hant creating build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/sessions/locale creating build/lib/django/contrib/sessions/locale/af creating build/lib/django/contrib/sessions/locale/af/LC_MESSAGES copying django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES copying django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ar creating build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ar_DZ creating build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ast creating build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/az creating build/lib/django/contrib/sessions/locale/az/LC_MESSAGES copying django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES copying django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/be creating build/lib/django/contrib/sessions/locale/be/LC_MESSAGES copying django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES copying django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/bg creating build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/bn creating build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/br creating build/lib/django/contrib/sessions/locale/br/LC_MESSAGES copying django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES copying django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/bs creating build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ca creating build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ckb creating build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/cs creating build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/cy creating build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/da creating build/lib/django/contrib/sessions/locale/da/LC_MESSAGES copying django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES copying django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/de creating build/lib/django/contrib/sessions/locale/de/LC_MESSAGES copying django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES copying django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/dsb creating build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/el creating build/lib/django/contrib/sessions/locale/el/LC_MESSAGES copying django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES copying django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/en creating build/lib/django/contrib/sessions/locale/en/LC_MESSAGES copying django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES copying django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/en_AU creating build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/en_GB creating build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/eo creating build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/es creating build/lib/django/contrib/sessions/locale/es/LC_MESSAGES copying django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES copying django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/es_AR creating build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/es_CO creating build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/es_MX creating build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/es_VE creating build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/et creating build/lib/django/contrib/sessions/locale/et/LC_MESSAGES copying django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES copying django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/eu creating build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/fa creating build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/fi creating build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/fr creating build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/fy creating build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ga creating build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/gd creating build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/gl creating build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/he creating build/lib/django/contrib/sessions/locale/he/LC_MESSAGES copying django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES copying django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/hi creating build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/hr creating build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/hsb creating build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/hu creating build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/hy creating build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ia creating build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/id creating build/lib/django/contrib/sessions/locale/id/LC_MESSAGES copying django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES copying django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/io creating build/lib/django/contrib/sessions/locale/io/LC_MESSAGES copying django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES copying django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/is creating build/lib/django/contrib/sessions/locale/is/LC_MESSAGES copying django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES copying django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/it creating build/lib/django/contrib/sessions/locale/it/LC_MESSAGES copying django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES copying django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ja creating build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ka creating build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/kab creating build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/kk creating build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/km creating build/lib/django/contrib/sessions/locale/km/LC_MESSAGES copying django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES copying django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/kn creating build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ko creating build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ky creating build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/lb creating build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/lt creating build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/lv creating build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/mk creating build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ml creating build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/mn creating build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/mr creating build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ms creating build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/my creating build/lib/django/contrib/sessions/locale/my/LC_MESSAGES copying django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES copying django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/nb creating build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ne creating build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/nl creating build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/nn creating build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/os creating build/lib/django/contrib/sessions/locale/os/LC_MESSAGES copying django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES copying django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/pa creating build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/pl creating build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/pt creating build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/pt_BR creating build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ro creating build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ru creating build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/sk creating build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/sl creating build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/sq creating build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/sr creating build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/sr_Latn creating build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/sv creating build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/sw creating build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ta creating build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/te creating build/lib/django/contrib/sessions/locale/te/LC_MESSAGES copying django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES copying django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/tg creating build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/th creating build/lib/django/contrib/sessions/locale/th/LC_MESSAGES copying django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES copying django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/tk creating build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/tr creating build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/tt creating build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/udm creating build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/uk creating build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/ur creating build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/uz creating build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/vi creating build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/zh_Hans creating build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/sessions/locale/zh_Hant creating build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/admin/locale creating build/lib/django/contrib/admin/locale/af creating build/lib/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES creating build/lib/django/contrib/admin/locale/am creating build/lib/django/contrib/admin/locale/am/LC_MESSAGES copying django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES copying django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ar creating build/lib/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ar_DZ creating build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ast creating build/lib/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES creating build/lib/django/contrib/admin/locale/az creating build/lib/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES creating build/lib/django/contrib/admin/locale/be creating build/lib/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES creating build/lib/django/contrib/admin/locale/bg creating build/lib/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES creating build/lib/django/contrib/admin/locale/bn creating build/lib/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES creating build/lib/django/contrib/admin/locale/br creating build/lib/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES creating build/lib/django/contrib/admin/locale/bs creating build/lib/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ca creating build/lib/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ckb creating build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/admin/locale/cs creating build/lib/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES creating build/lib/django/contrib/admin/locale/cy creating build/lib/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES creating build/lib/django/contrib/admin/locale/da creating build/lib/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES creating build/lib/django/contrib/admin/locale/de creating build/lib/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES creating build/lib/django/contrib/admin/locale/dsb creating build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/admin/locale/el creating build/lib/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES creating build/lib/django/contrib/admin/locale/en creating build/lib/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES creating build/lib/django/contrib/admin/locale/en_AU creating build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/admin/locale/en_GB creating build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/admin/locale/eo creating build/lib/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES creating build/lib/django/contrib/admin/locale/es creating build/lib/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES creating build/lib/django/contrib/admin/locale/es_AR creating build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/admin/locale/es_CO creating build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/admin/locale/es_MX creating build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/admin/locale/es_VE creating build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/admin/locale/et creating build/lib/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES creating build/lib/django/contrib/admin/locale/eu creating build/lib/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES creating build/lib/django/contrib/admin/locale/fa creating build/lib/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES creating build/lib/django/contrib/admin/locale/fi creating build/lib/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES creating build/lib/django/contrib/admin/locale/fr creating build/lib/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES creating build/lib/django/contrib/admin/locale/fy creating build/lib/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ga creating build/lib/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES creating build/lib/django/contrib/admin/locale/gd creating build/lib/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES creating build/lib/django/contrib/admin/locale/gl creating build/lib/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES creating build/lib/django/contrib/admin/locale/he creating build/lib/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES creating build/lib/django/contrib/admin/locale/hi creating build/lib/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES creating build/lib/django/contrib/admin/locale/hr creating build/lib/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES creating build/lib/django/contrib/admin/locale/hsb creating build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/admin/locale/hu creating build/lib/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES creating build/lib/django/contrib/admin/locale/hy creating build/lib/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ia creating build/lib/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES creating build/lib/django/contrib/admin/locale/id creating build/lib/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES creating build/lib/django/contrib/admin/locale/io creating build/lib/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES creating build/lib/django/contrib/admin/locale/is creating build/lib/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES creating build/lib/django/contrib/admin/locale/it creating build/lib/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ja creating build/lib/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ka creating build/lib/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES creating build/lib/django/contrib/admin/locale/kab creating build/lib/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES creating build/lib/django/contrib/admin/locale/kk creating build/lib/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES creating build/lib/django/contrib/admin/locale/km creating build/lib/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES creating build/lib/django/contrib/admin/locale/kn creating build/lib/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ko creating build/lib/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ky creating build/lib/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES creating build/lib/django/contrib/admin/locale/lb creating build/lib/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES creating build/lib/django/contrib/admin/locale/lt creating build/lib/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES creating build/lib/django/contrib/admin/locale/lv creating build/lib/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES creating build/lib/django/contrib/admin/locale/mk creating build/lib/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ml creating build/lib/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES creating build/lib/django/contrib/admin/locale/mn creating build/lib/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES creating build/lib/django/contrib/admin/locale/mr creating build/lib/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ms creating build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES creating build/lib/django/contrib/admin/locale/my creating build/lib/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES creating build/lib/django/contrib/admin/locale/nb creating build/lib/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ne creating build/lib/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES creating build/lib/django/contrib/admin/locale/nl creating build/lib/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES creating build/lib/django/contrib/admin/locale/nn creating build/lib/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES creating build/lib/django/contrib/admin/locale/os creating build/lib/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES creating build/lib/django/contrib/admin/locale/pa creating build/lib/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES creating build/lib/django/contrib/admin/locale/pl creating build/lib/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES creating build/lib/django/contrib/admin/locale/pt creating build/lib/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES creating build/lib/django/contrib/admin/locale/pt_BR creating build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ro creating build/lib/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ru creating build/lib/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES creating build/lib/django/contrib/admin/locale/sk creating build/lib/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES creating build/lib/django/contrib/admin/locale/sl creating build/lib/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES creating build/lib/django/contrib/admin/locale/sq creating build/lib/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES creating build/lib/django/contrib/admin/locale/sr creating build/lib/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES creating build/lib/django/contrib/admin/locale/sr_Latn creating build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/admin/locale/sv creating build/lib/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES creating build/lib/django/contrib/admin/locale/sw creating build/lib/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ta creating build/lib/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES creating build/lib/django/contrib/admin/locale/te creating build/lib/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES creating build/lib/django/contrib/admin/locale/tg creating build/lib/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES creating build/lib/django/contrib/admin/locale/th creating build/lib/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES creating build/lib/django/contrib/admin/locale/tk creating build/lib/django/contrib/admin/locale/tk/LC_MESSAGES copying django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES copying django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES creating build/lib/django/contrib/admin/locale/tr creating build/lib/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES creating build/lib/django/contrib/admin/locale/tt creating build/lib/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES creating build/lib/django/contrib/admin/locale/udm creating build/lib/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES creating build/lib/django/contrib/admin/locale/uk creating build/lib/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES creating build/lib/django/contrib/admin/locale/ur creating build/lib/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES creating build/lib/django/contrib/admin/locale/uz creating build/lib/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES creating build/lib/django/contrib/admin/locale/vi creating build/lib/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES creating build/lib/django/contrib/admin/locale/zh_Hans creating build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/admin/locale/zh_Hant creating build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/admin/static creating build/lib/django/contrib/admin/static/admin creating build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/autocomplete.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/base.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/changelists.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/dark_mode.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/dashboard.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/forms.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/login.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/nav_sidebar.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/responsive.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/responsive_rtl.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/rtl.css -> build/lib/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/widgets.css -> build/lib/django/contrib/admin/static/admin/css creating build/lib/django/contrib/admin/static/admin/css/vendor creating build/lib/django/contrib/admin/static/admin/css/vendor/select2 copying django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/lib/django/contrib/admin/static/admin/css/vendor/select2 copying django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2 copying django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2 creating build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/LICENSE -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/README.txt -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/calendar-icons.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-addlink.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-alert.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-calendar.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-changelink.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-clock.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-no.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-unknown.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-yes.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/inline-delete.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/search.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/selector-icons.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/sorting-icons.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/tooltag-add.svg -> build/lib/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/lib/django/contrib/admin/static/admin/img creating build/lib/django/contrib/admin/static/admin/img/gis copying django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/lib/django/contrib/admin/static/admin/img/gis copying django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/lib/django/contrib/admin/static/admin/img/gis creating build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/SelectBox.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/SelectFilter2.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/actions.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/autocomplete.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/calendar.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/cancel.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/change_form.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/collapse.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/core.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/filters.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/inlines.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/jquery.init.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/nav_sidebar.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/popup_response.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/prepopulate.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/prepopulate_init.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/theme.js -> build/lib/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/urlify.js -> build/lib/django/contrib/admin/static/admin/js creating build/lib/django/contrib/admin/static/admin/js/admin copying django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/lib/django/contrib/admin/static/admin/js/admin copying django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/lib/django/contrib/admin/static/admin/js/admin creating build/lib/django/contrib/admin/static/admin/js/vendor creating build/lib/django/contrib/admin/static/admin/js/vendor/jquery copying django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery creating build/lib/django/contrib/admin/static/admin/js/vendor/select2 copying django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/lib/django/contrib/admin/static/admin/js/vendor/select2 copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2 copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2 creating build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n creating build/lib/django/contrib/admin/static/admin/js/vendor/xregexp copying django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp creating build/lib/django/contrib/admin/templates creating build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/404.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/500.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/actions.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/app_index.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/app_list.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/base.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/base_site.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_form.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_form_object_tools.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_list.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_list_object_tools.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_list_results.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/color_theme_toggle.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/date_hierarchy.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/delete_confirmation.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/filter.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/index.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/invalid_setup.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/login.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/nav_sidebar.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/object_history.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/pagination.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/popup_response.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/search_form.html -> build/lib/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/submit_line.html -> build/lib/django/contrib/admin/templates/admin creating build/lib/django/contrib/admin/templates/admin/auth creating build/lib/django/contrib/admin/templates/admin/auth/user copying django/contrib/admin/templates/admin/auth/user/add_form.html -> build/lib/django/contrib/admin/templates/admin/auth/user copying django/contrib/admin/templates/admin/auth/user/change_password.html -> build/lib/django/contrib/admin/templates/admin/auth/user creating build/lib/django/contrib/admin/templates/admin/edit_inline copying django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/lib/django/contrib/admin/templates/admin/edit_inline copying django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/lib/django/contrib/admin/templates/admin/edit_inline creating build/lib/django/contrib/admin/templates/admin/includes copying django/contrib/admin/templates/admin/includes/fieldset.html -> build/lib/django/contrib/admin/templates/admin/includes copying django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/lib/django/contrib/admin/templates/admin/includes creating build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/date.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/radio.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/time.html -> build/lib/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/url.html -> build/lib/django/contrib/admin/templates/admin/widgets creating build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/logged_out.html -> build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_change_done.html -> build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_change_form.html -> build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_complete.html -> build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_confirm.html -> build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_done.html -> build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_email.html -> build/lib/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_form.html -> build/lib/django/contrib/admin/templates/registration creating build/lib/django/contrib/postgres/jinja2 creating build/lib/django/contrib/postgres/jinja2/postgres creating build/lib/django/contrib/postgres/jinja2/postgres/widgets copying django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/jinja2/postgres/widgets creating build/lib/django/contrib/postgres/locale creating build/lib/django/contrib/postgres/locale/af creating build/lib/django/contrib/postgres/locale/af/LC_MESSAGES copying django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES copying django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ar creating build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ar_DZ creating build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/az creating build/lib/django/contrib/postgres/locale/az/LC_MESSAGES copying django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES copying django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/be creating build/lib/django/contrib/postgres/locale/be/LC_MESSAGES copying django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES copying django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/bg creating build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ca creating build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ckb creating build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/cs creating build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/da creating build/lib/django/contrib/postgres/locale/da/LC_MESSAGES copying django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES copying django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/de creating build/lib/django/contrib/postgres/locale/de/LC_MESSAGES copying django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES copying django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/dsb creating build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/el creating build/lib/django/contrib/postgres/locale/el/LC_MESSAGES copying django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES copying django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/en creating build/lib/django/contrib/postgres/locale/en/LC_MESSAGES copying django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES copying django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/en_AU creating build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/eo creating build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/es creating build/lib/django/contrib/postgres/locale/es/LC_MESSAGES copying django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES copying django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/es_AR creating build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/es_CO creating build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/es_MX creating build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/et creating build/lib/django/contrib/postgres/locale/et/LC_MESSAGES copying django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES copying django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/eu creating build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/fa creating build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/fi creating build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/fr creating build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/gd creating build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/gl creating build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/he creating build/lib/django/contrib/postgres/locale/he/LC_MESSAGES copying django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES copying django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/hr creating build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/hsb creating build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/hu creating build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/hy creating build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ia creating build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/id creating build/lib/django/contrib/postgres/locale/id/LC_MESSAGES copying django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES copying django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/is creating build/lib/django/contrib/postgres/locale/is/LC_MESSAGES copying django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES copying django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/it creating build/lib/django/contrib/postgres/locale/it/LC_MESSAGES copying django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES copying django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ja creating build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ka creating build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/kk creating build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ko creating build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ky creating build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/lt creating build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/lv creating build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/mk creating build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ml creating build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/mn creating build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ms creating build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/nb creating build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ne creating build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/nl creating build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/nn creating build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/pl creating build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/pt creating build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/pt_BR creating build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ro creating build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/ru creating build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/sk creating build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/sl creating build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/sq creating build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/sr creating build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/sr_Latn creating build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/sv creating build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/tg creating build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/tk creating build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/tr creating build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/uk creating build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/uz creating build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/zh_Hans creating build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/postgres/locale/zh_Hant creating build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/postgres/templates creating build/lib/django/contrib/postgres/templates/postgres creating build/lib/django/contrib/postgres/templates/postgres/widgets copying django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/templates/postgres/widgets creating build/lib/django/contrib/admindocs/locale creating build/lib/django/contrib/admindocs/locale/af creating build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ar creating build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ar_DZ creating build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ast creating build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/az creating build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/be creating build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/bg creating build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/bn creating build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/br creating build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/bs creating build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ca creating build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ckb creating build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/cs creating build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/cy creating build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/da creating build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/de creating build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/dsb creating build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/el creating build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/en creating build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/en_AU creating build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/en_GB creating build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/eo creating build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/es creating build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/es_AR creating build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/es_CO creating build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/es_MX creating build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/es_VE creating build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/et creating build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/eu creating build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/fa creating build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/fi creating build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/fr creating build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/fy creating build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ga creating build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/gd creating build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/gl creating build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/he creating build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/hi creating build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/hr creating build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/hsb creating build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/hu creating build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ia creating build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/id creating build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/io creating build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/is creating build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/it creating build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ja creating build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ka creating build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/kab creating build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/kk creating build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/km creating build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/kn creating build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ko creating build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ky creating build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/lb creating build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/lt creating build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/lv creating build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/mk creating build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ml creating build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/mn creating build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/mr creating build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ms creating build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/my creating build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/nb creating build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ne creating build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/nl creating build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/nn creating build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/os creating build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/pa creating build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/pl creating build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/pt creating build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/pt_BR creating build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ro creating build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ru creating build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/sk creating build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/sl creating build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/sq creating build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/sr creating build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/sr_Latn creating build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/sv creating build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/sw creating build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ta creating build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/te creating build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/tg creating build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/th creating build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/tr creating build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/tt creating build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/udm creating build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/uk creating build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/ur creating build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/vi creating build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/zh_Hans creating build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES creating build/lib/django/contrib/admindocs/locale/zh_Hant creating build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES creating build/lib/django/contrib/admindocs/templates creating build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/index.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/model_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/view_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc copying django/contrib/gis/gdal/LICENSE -> build/lib/django/contrib/gis/gdal copying django/contrib/gis/geos/LICENSE -> build/lib/django/contrib/gis/geos creating build/lib/django/conf/locale/af creating build/lib/django/conf/locale/af/LC_MESSAGES copying django/conf/locale/af/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/af/LC_MESSAGES copying django/conf/locale/af/LC_MESSAGES/django.po -> build/lib/django/conf/locale/af/LC_MESSAGES creating build/lib/django/conf/locale/ast creating build/lib/django/conf/locale/ast/LC_MESSAGES copying django/conf/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ast/LC_MESSAGES copying django/conf/locale/ast/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ast/LC_MESSAGES creating build/lib/django/conf/locale/be creating build/lib/django/conf/locale/be/LC_MESSAGES copying django/conf/locale/be/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/be/LC_MESSAGES copying django/conf/locale/be/LC_MESSAGES/django.po -> build/lib/django/conf/locale/be/LC_MESSAGES creating build/lib/django/conf/locale/br creating build/lib/django/conf/locale/br/LC_MESSAGES copying django/conf/locale/br/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/br/LC_MESSAGES copying django/conf/locale/br/LC_MESSAGES/django.po -> build/lib/django/conf/locale/br/LC_MESSAGES creating build/lib/django/conf/locale/dsb creating build/lib/django/conf/locale/dsb/LC_MESSAGES copying django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/dsb/LC_MESSAGES copying django/conf/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/dsb/LC_MESSAGES creating build/lib/django/conf/locale/es_VE creating build/lib/django/conf/locale/es_VE/LC_MESSAGES copying django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_VE/LC_MESSAGES copying django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_VE/LC_MESSAGES creating build/lib/django/conf/locale/hsb creating build/lib/django/conf/locale/hsb/LC_MESSAGES copying django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hsb/LC_MESSAGES copying django/conf/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hsb/LC_MESSAGES creating build/lib/django/conf/locale/hy creating build/lib/django/conf/locale/hy/LC_MESSAGES copying django/conf/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hy/LC_MESSAGES copying django/conf/locale/hy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hy/LC_MESSAGES creating build/lib/django/conf/locale/ia creating build/lib/django/conf/locale/ia/LC_MESSAGES copying django/conf/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ia/LC_MESSAGES copying django/conf/locale/ia/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ia/LC_MESSAGES creating build/lib/django/conf/locale/io creating build/lib/django/conf/locale/io/LC_MESSAGES copying django/conf/locale/io/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/io/LC_MESSAGES copying django/conf/locale/io/LC_MESSAGES/django.po -> build/lib/django/conf/locale/io/LC_MESSAGES creating build/lib/django/conf/locale/kab creating build/lib/django/conf/locale/kab/LC_MESSAGES copying django/conf/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kab/LC_MESSAGES copying django/conf/locale/kab/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kab/LC_MESSAGES creating build/lib/django/conf/locale/kk creating build/lib/django/conf/locale/kk/LC_MESSAGES copying django/conf/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kk/LC_MESSAGES copying django/conf/locale/kk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kk/LC_MESSAGES creating build/lib/django/conf/locale/lb creating build/lib/django/conf/locale/lb/LC_MESSAGES copying django/conf/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lb/LC_MESSAGES copying django/conf/locale/lb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lb/LC_MESSAGES creating build/lib/django/conf/locale/mr creating build/lib/django/conf/locale/mr/LC_MESSAGES copying django/conf/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mr/LC_MESSAGES copying django/conf/locale/mr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mr/LC_MESSAGES creating build/lib/django/conf/locale/my creating build/lib/django/conf/locale/my/LC_MESSAGES copying django/conf/locale/my/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/my/LC_MESSAGES copying django/conf/locale/my/LC_MESSAGES/django.po -> build/lib/django/conf/locale/my/LC_MESSAGES creating build/lib/django/conf/locale/ne creating build/lib/django/conf/locale/ne/LC_MESSAGES copying django/conf/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ne/LC_MESSAGES copying django/conf/locale/ne/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ne/LC_MESSAGES creating build/lib/django/conf/locale/os creating build/lib/django/conf/locale/os/LC_MESSAGES copying django/conf/locale/os/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/os/LC_MESSAGES copying django/conf/locale/os/LC_MESSAGES/django.po -> build/lib/django/conf/locale/os/LC_MESSAGES creating build/lib/django/conf/locale/pa creating build/lib/django/conf/locale/pa/LC_MESSAGES copying django/conf/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pa/LC_MESSAGES copying django/conf/locale/pa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pa/LC_MESSAGES creating build/lib/django/conf/locale/sw creating build/lib/django/conf/locale/sw/LC_MESSAGES copying django/conf/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sw/LC_MESSAGES copying django/conf/locale/sw/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sw/LC_MESSAGES creating build/lib/django/conf/locale/tt creating build/lib/django/conf/locale/tt/LC_MESSAGES copying django/conf/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tt/LC_MESSAGES copying django/conf/locale/tt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tt/LC_MESSAGES creating build/lib/django/conf/locale/udm creating build/lib/django/conf/locale/udm/LC_MESSAGES copying django/conf/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/udm/LC_MESSAGES copying django/conf/locale/udm/LC_MESSAGES/django.po -> build/lib/django/conf/locale/udm/LC_MESSAGES creating build/lib/django/conf/locale/ur creating build/lib/django/conf/locale/ur/LC_MESSAGES copying django/conf/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ur/LC_MESSAGES copying django/conf/locale/ur/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ur/LC_MESSAGES creating build/lib/django/conf/locale/ms/LC_MESSAGES copying django/conf/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ms/LC_MESSAGES copying django/conf/locale/ms/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ms/LC_MESSAGES creating build/lib/django/conf/locale/gl/LC_MESSAGES copying django/conf/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gl/LC_MESSAGES copying django/conf/locale/gl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gl/LC_MESSAGES creating build/lib/django/conf/locale/sr_Latn/LC_MESSAGES copying django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES copying django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES creating build/lib/django/conf/locale/pt_BR/LC_MESSAGES copying django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES copying django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES creating build/lib/django/conf/locale/pl/LC_MESSAGES copying django/conf/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pl/LC_MESSAGES copying django/conf/locale/pl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pl/LC_MESSAGES creating build/lib/django/conf/locale/es/LC_MESSAGES copying django/conf/locale/es/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es/LC_MESSAGES copying django/conf/locale/es/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es/LC_MESSAGES creating build/lib/django/conf/locale/hu/LC_MESSAGES copying django/conf/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hu/LC_MESSAGES copying django/conf/locale/hu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hu/LC_MESSAGES creating build/lib/django/conf/locale/hr/LC_MESSAGES copying django/conf/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hr/LC_MESSAGES copying django/conf/locale/hr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hr/LC_MESSAGES creating build/lib/django/conf/locale/et/LC_MESSAGES copying django/conf/locale/et/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/et/LC_MESSAGES copying django/conf/locale/et/LC_MESSAGES/django.po -> build/lib/django/conf/locale/et/LC_MESSAGES creating build/lib/django/conf/locale/bs/LC_MESSAGES copying django/conf/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bs/LC_MESSAGES copying django/conf/locale/bs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bs/LC_MESSAGES creating build/lib/django/conf/locale/kn/LC_MESSAGES copying django/conf/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kn/LC_MESSAGES copying django/conf/locale/kn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kn/LC_MESSAGES creating build/lib/django/conf/locale/bg/LC_MESSAGES copying django/conf/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bg/LC_MESSAGES copying django/conf/locale/bg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bg/LC_MESSAGES creating build/lib/django/conf/locale/ar_DZ/LC_MESSAGES copying django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES copying django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES creating build/lib/django/conf/locale/nb/LC_MESSAGES copying django/conf/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nb/LC_MESSAGES copying django/conf/locale/nb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nb/LC_MESSAGES creating build/lib/django/conf/locale/ga/LC_MESSAGES copying django/conf/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ga/LC_MESSAGES copying django/conf/locale/ga/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ga/LC_MESSAGES creating build/lib/django/conf/locale/mn/LC_MESSAGES copying django/conf/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mn/LC_MESSAGES copying django/conf/locale/mn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mn/LC_MESSAGES creating build/lib/django/conf/locale/es_CO/LC_MESSAGES copying django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_CO/LC_MESSAGES copying django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_CO/LC_MESSAGES creating build/lib/django/conf/locale/nl/LC_MESSAGES copying django/conf/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nl/LC_MESSAGES copying django/conf/locale/nl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nl/LC_MESSAGES creating build/lib/django/conf/locale/en/LC_MESSAGES copying django/conf/locale/en/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en/LC_MESSAGES copying django/conf/locale/en/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en/LC_MESSAGES creating build/lib/django/conf/locale/fr/LC_MESSAGES copying django/conf/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fr/LC_MESSAGES copying django/conf/locale/fr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fr/LC_MESSAGES creating build/lib/django/conf/locale/en_AU/LC_MESSAGES copying django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_AU/LC_MESSAGES copying django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_AU/LC_MESSAGES creating build/lib/django/conf/locale/he/LC_MESSAGES copying django/conf/locale/he/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/he/LC_MESSAGES copying django/conf/locale/he/LC_MESSAGES/django.po -> build/lib/django/conf/locale/he/LC_MESSAGES creating build/lib/django/conf/locale/fa/LC_MESSAGES copying django/conf/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fa/LC_MESSAGES copying django/conf/locale/fa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fa/LC_MESSAGES creating build/lib/django/conf/locale/tg/LC_MESSAGES copying django/conf/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tg/LC_MESSAGES copying django/conf/locale/tg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tg/LC_MESSAGES creating build/lib/django/conf/locale/ar/LC_MESSAGES copying django/conf/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar/LC_MESSAGES copying django/conf/locale/ar/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar/LC_MESSAGES creating build/lib/django/conf/locale/bn/LC_MESSAGES copying django/conf/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bn/LC_MESSAGES copying django/conf/locale/bn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bn/LC_MESSAGES creating build/lib/django/conf/locale/km/LC_MESSAGES copying django/conf/locale/km/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/km/LC_MESSAGES copying django/conf/locale/km/LC_MESSAGES/django.po -> build/lib/django/conf/locale/km/LC_MESSAGES creating build/lib/django/conf/locale/ky/LC_MESSAGES copying django/conf/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ky/LC_MESSAGES copying django/conf/locale/ky/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ky/LC_MESSAGES creating build/lib/django/conf/locale/lt/LC_MESSAGES copying django/conf/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lt/LC_MESSAGES copying django/conf/locale/lt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lt/LC_MESSAGES creating build/lib/django/conf/locale/uz/LC_MESSAGES copying django/conf/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uz/LC_MESSAGES copying django/conf/locale/uz/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uz/LC_MESSAGES creating build/lib/django/conf/locale/en_GB/LC_MESSAGES copying django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_GB/LC_MESSAGES copying django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_GB/LC_MESSAGES creating build/lib/django/conf/locale/es_MX/LC_MESSAGES copying django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_MX/LC_MESSAGES copying django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_MX/LC_MESSAGES creating build/lib/django/conf/locale/cy/LC_MESSAGES copying django/conf/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cy/LC_MESSAGES copying django/conf/locale/cy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cy/LC_MESSAGES creating build/lib/django/conf/locale/cs/LC_MESSAGES copying django/conf/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cs/LC_MESSAGES copying django/conf/locale/cs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cs/LC_MESSAGES creating build/lib/django/conf/locale/zh_Hant/LC_MESSAGES copying django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES copying django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES creating build/lib/django/conf/locale/ru/LC_MESSAGES copying django/conf/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ru/LC_MESSAGES copying django/conf/locale/ru/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ru/LC_MESSAGES creating build/lib/django/conf/locale/id/LC_MESSAGES copying django/conf/locale/id/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/id/LC_MESSAGES copying django/conf/locale/id/LC_MESSAGES/django.po -> build/lib/django/conf/locale/id/LC_MESSAGES creating build/lib/django/conf/locale/mk/LC_MESSAGES copying django/conf/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mk/LC_MESSAGES copying django/conf/locale/mk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mk/LC_MESSAGES creating build/lib/django/conf/locale/te/LC_MESSAGES copying django/conf/locale/te/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/te/LC_MESSAGES copying django/conf/locale/te/LC_MESSAGES/django.po -> build/lib/django/conf/locale/te/LC_MESSAGES creating build/lib/django/conf/locale/az/LC_MESSAGES copying django/conf/locale/az/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/az/LC_MESSAGES copying django/conf/locale/az/LC_MESSAGES/django.po -> build/lib/django/conf/locale/az/LC_MESSAGES creating build/lib/django/conf/locale/fi/LC_MESSAGES copying django/conf/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fi/LC_MESSAGES copying django/conf/locale/fi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fi/LC_MESSAGES creating build/lib/django/conf/locale/sv/LC_MESSAGES copying django/conf/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sv/LC_MESSAGES copying django/conf/locale/sv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sv/LC_MESSAGES creating build/lib/django/conf/locale/eu/LC_MESSAGES copying django/conf/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eu/LC_MESSAGES copying django/conf/locale/eu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eu/LC_MESSAGES creating build/lib/django/conf/locale/lv/LC_MESSAGES copying django/conf/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lv/LC_MESSAGES copying django/conf/locale/lv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lv/LC_MESSAGES creating build/lib/django/conf/locale/pt/LC_MESSAGES copying django/conf/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt/LC_MESSAGES copying django/conf/locale/pt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt/LC_MESSAGES creating build/lib/django/conf/locale/ko/LC_MESSAGES copying django/conf/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ko/LC_MESSAGES copying django/conf/locale/ko/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ko/LC_MESSAGES creating build/lib/django/conf/locale/el/LC_MESSAGES copying django/conf/locale/el/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/el/LC_MESSAGES copying django/conf/locale/el/LC_MESSAGES/django.po -> build/lib/django/conf/locale/el/LC_MESSAGES creating build/lib/django/conf/locale/sq/LC_MESSAGES copying django/conf/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sq/LC_MESSAGES copying django/conf/locale/sq/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sq/LC_MESSAGES creating build/lib/django/conf/locale/es_AR/LC_MESSAGES copying django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_AR/LC_MESSAGES copying django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_AR/LC_MESSAGES creating build/lib/django/conf/locale/th/LC_MESSAGES copying django/conf/locale/th/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/th/LC_MESSAGES copying django/conf/locale/th/LC_MESSAGES/django.po -> build/lib/django/conf/locale/th/LC_MESSAGES creating build/lib/django/conf/locale/ml/LC_MESSAGES copying django/conf/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ml/LC_MESSAGES copying django/conf/locale/ml/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ml/LC_MESSAGES creating build/lib/django/conf/locale/de/LC_MESSAGES copying django/conf/locale/de/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/de/LC_MESSAGES copying django/conf/locale/de/LC_MESSAGES/django.po -> build/lib/django/conf/locale/de/LC_MESSAGES creating build/lib/django/conf/locale/ja/LC_MESSAGES copying django/conf/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ja/LC_MESSAGES copying django/conf/locale/ja/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ja/LC_MESSAGES creating build/lib/django/conf/locale/vi/LC_MESSAGES copying django/conf/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/vi/LC_MESSAGES copying django/conf/locale/vi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/vi/LC_MESSAGES creating build/lib/django/conf/locale/nn/LC_MESSAGES copying django/conf/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nn/LC_MESSAGES copying django/conf/locale/nn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nn/LC_MESSAGES creating build/lib/django/conf/locale/zh_Hans/LC_MESSAGES copying django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES copying django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES creating build/lib/django/conf/locale/uk/LC_MESSAGES copying django/conf/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uk/LC_MESSAGES copying django/conf/locale/uk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uk/LC_MESSAGES creating build/lib/django/conf/locale/ig/LC_MESSAGES copying django/conf/locale/ig/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ig/LC_MESSAGES copying django/conf/locale/ig/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ig/LC_MESSAGES creating build/lib/django/conf/locale/is/LC_MESSAGES copying django/conf/locale/is/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/is/LC_MESSAGES copying django/conf/locale/is/LC_MESSAGES/django.po -> build/lib/django/conf/locale/is/LC_MESSAGES creating build/lib/django/conf/locale/da/LC_MESSAGES copying django/conf/locale/da/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/da/LC_MESSAGES copying django/conf/locale/da/LC_MESSAGES/django.po -> build/lib/django/conf/locale/da/LC_MESSAGES creating build/lib/django/conf/locale/tr/LC_MESSAGES copying django/conf/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tr/LC_MESSAGES copying django/conf/locale/tr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tr/LC_MESSAGES creating build/lib/django/conf/locale/sk/LC_MESSAGES copying django/conf/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sk/LC_MESSAGES copying django/conf/locale/sk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sk/LC_MESSAGES creating build/lib/django/conf/locale/eo/LC_MESSAGES copying django/conf/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eo/LC_MESSAGES copying django/conf/locale/eo/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eo/LC_MESSAGES creating build/lib/django/conf/locale/ka/LC_MESSAGES copying django/conf/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ka/LC_MESSAGES copying django/conf/locale/ka/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ka/LC_MESSAGES creating build/lib/django/conf/locale/sl/LC_MESSAGES copying django/conf/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sl/LC_MESSAGES copying django/conf/locale/sl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sl/LC_MESSAGES creating build/lib/django/conf/locale/tk/LC_MESSAGES copying django/conf/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tk/LC_MESSAGES copying django/conf/locale/tk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tk/LC_MESSAGES creating build/lib/django/conf/locale/fy/LC_MESSAGES copying django/conf/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fy/LC_MESSAGES copying django/conf/locale/fy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fy/LC_MESSAGES creating build/lib/django/conf/locale/ta/LC_MESSAGES copying django/conf/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ta/LC_MESSAGES copying django/conf/locale/ta/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ta/LC_MESSAGES creating build/lib/django/conf/locale/sr/LC_MESSAGES copying django/conf/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr/LC_MESSAGES copying django/conf/locale/sr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr/LC_MESSAGES creating build/lib/django/conf/locale/hi/LC_MESSAGES copying django/conf/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hi/LC_MESSAGES copying django/conf/locale/hi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hi/LC_MESSAGES creating build/lib/django/conf/locale/ckb/LC_MESSAGES copying django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ckb/LC_MESSAGES copying django/conf/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ckb/LC_MESSAGES creating build/lib/django/conf/locale/ca/LC_MESSAGES copying django/conf/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ca/LC_MESSAGES copying django/conf/locale/ca/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ca/LC_MESSAGES creating build/lib/django/conf/locale/ro/LC_MESSAGES copying django/conf/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ro/LC_MESSAGES copying django/conf/locale/ro/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ro/LC_MESSAGES creating build/lib/django/conf/locale/it/LC_MESSAGES copying django/conf/locale/it/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/it/LC_MESSAGES copying django/conf/locale/it/LC_MESSAGES/django.po -> build/lib/django/conf/locale/it/LC_MESSAGES creating build/lib/django/conf/locale/gd/LC_MESSAGES copying django/conf/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gd/LC_MESSAGES copying django/conf/locale/gd/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gd/LC_MESSAGES installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/django creating build/bdist.linux-x86_64/wheel/django/core copying build/lib/django/core/__init__.py -> build/bdist.linux-x86_64/wheel/django/core copying build/lib/django/core/validators.py -> build/bdist.linux-x86_64/wheel/django/core creating build/bdist.linux-x86_64/wheel/django/core/management copying build/lib/django/core/management/templates.py -> build/bdist.linux-x86_64/wheel/django/core/management copying build/lib/django/core/management/base.py -> build/bdist.linux-x86_64/wheel/django/core/management creating build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/testserver.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/sqlflush.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/check.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/showmigrations.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/compilemessages.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/startapp.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/makemessages.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/runserver.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/inspectdb.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/migrate.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/squashmigrations.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/dbshell.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/makemigrations.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/optimizemigration.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/test.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/createcachetable.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/sqlsequencereset.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/sendtestemail.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/loaddata.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/shell.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/flush.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/startproject.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/diffsettings.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/dumpdata.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/commands/sqlmigrate.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands copying build/lib/django/core/management/sql.py -> build/bdist.linux-x86_64/wheel/django/core/management copying build/lib/django/core/management/utils.py -> build/bdist.linux-x86_64/wheel/django/core/management copying build/lib/django/core/management/color.py -> build/bdist.linux-x86_64/wheel/django/core/management copying build/lib/django/core/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/management creating build/bdist.linux-x86_64/wheel/django/core/mail copying build/lib/django/core/mail/message.py -> build/bdist.linux-x86_64/wheel/django/core/mail creating build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/backends/smtp.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/backends/base.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/backends/filebased.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/backends/locmem.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/backends/console.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/backends/dummy.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends copying build/lib/django/core/mail/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/mail copying build/lib/django/core/mail/utils.py -> build/bdist.linux-x86_64/wheel/django/core/mail copying build/lib/django/core/asgi.py -> build/bdist.linux-x86_64/wheel/django/core copying build/lib/django/core/signals.py -> build/bdist.linux-x86_64/wheel/django/core creating build/bdist.linux-x86_64/wheel/django/core/cache copying build/lib/django/core/cache/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/cache creating build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/db.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/locmem.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/filebased.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/redis.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/dummy.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/base.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/backends/memcached.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends copying build/lib/django/core/cache/utils.py -> build/bdist.linux-x86_64/wheel/django/core/cache copying build/lib/django/core/wsgi.py -> build/bdist.linux-x86_64/wheel/django/core creating build/bdist.linux-x86_64/wheel/django/core/serializers copying build/lib/django/core/serializers/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/serializers copying build/lib/django/core/serializers/jsonl.py -> build/bdist.linux-x86_64/wheel/django/core/serializers copying build/lib/django/core/serializers/python.py -> build/bdist.linux-x86_64/wheel/django/core/serializers copying build/lib/django/core/serializers/json.py -> build/bdist.linux-x86_64/wheel/django/core/serializers copying build/lib/django/core/serializers/base.py -> build/bdist.linux-x86_64/wheel/django/core/serializers copying build/lib/django/core/serializers/pyyaml.py -> build/bdist.linux-x86_64/wheel/django/core/serializers copying build/lib/django/core/serializers/xml_serializer.py -> build/bdist.linux-x86_64/wheel/django/core/serializers creating build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/translation.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/database.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/registry.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/async_checks.py -> build/bdist.linux-x86_64/wheel/django/core/checks creating build/bdist.linux-x86_64/wheel/django/core/checks/compatibility copying build/lib/django/core/checks/compatibility/django_4_0.py -> build/bdist.linux-x86_64/wheel/django/core/checks/compatibility copying build/lib/django/core/checks/compatibility/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/checks/compatibility copying build/lib/django/core/checks/caches.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/urls.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/model_checks.py -> build/bdist.linux-x86_64/wheel/django/core/checks creating build/bdist.linux-x86_64/wheel/django/core/checks/security copying build/lib/django/core/checks/security/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security copying build/lib/django/core/checks/security/sessions.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security copying build/lib/django/core/checks/security/base.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security copying build/lib/django/core/checks/security/csrf.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security copying build/lib/django/core/checks/templates.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/files.py -> build/bdist.linux-x86_64/wheel/django/core/checks copying build/lib/django/core/checks/messages.py -> build/bdist.linux-x86_64/wheel/django/core/checks creating build/bdist.linux-x86_64/wheel/django/core/servers copying build/lib/django/core/servers/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/servers copying build/lib/django/core/servers/basehttp.py -> build/bdist.linux-x86_64/wheel/django/core/servers copying build/lib/django/core/exceptions.py -> build/bdist.linux-x86_64/wheel/django/core copying build/lib/django/core/signing.py -> build/bdist.linux-x86_64/wheel/django/core creating build/bdist.linux-x86_64/wheel/django/core/handlers copying build/lib/django/core/handlers/exception.py -> build/bdist.linux-x86_64/wheel/django/core/handlers copying build/lib/django/core/handlers/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/handlers copying build/lib/django/core/handlers/wsgi.py -> build/bdist.linux-x86_64/wheel/django/core/handlers copying build/lib/django/core/handlers/asgi.py -> build/bdist.linux-x86_64/wheel/django/core/handlers copying build/lib/django/core/handlers/base.py -> build/bdist.linux-x86_64/wheel/django/core/handlers creating build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/uploadedfile.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/images.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/temp.py -> build/bdist.linux-x86_64/wheel/django/core/files creating build/bdist.linux-x86_64/wheel/django/core/files/storage copying build/lib/django/core/files/storage/mixins.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage copying build/lib/django/core/files/storage/filesystem.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage copying build/lib/django/core/files/storage/handler.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage copying build/lib/django/core/files/storage/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage copying build/lib/django/core/files/storage/base.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage copying build/lib/django/core/files/storage/memory.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage copying build/lib/django/core/files/move.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/base.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/locks.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/utils.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/files/uploadhandler.py -> build/bdist.linux-x86_64/wheel/django/core/files copying build/lib/django/core/paginator.py -> build/bdist.linux-x86_64/wheel/django/core creating build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/csrf.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/http.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/cache.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/clickjacking.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/locale.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/common.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/security.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/gzip.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/middleware/__init__.py -> build/bdist.linux-x86_64/wheel/django/middleware copying build/lib/django/__init__.py -> build/bdist.linux-x86_64/wheel/django creating build/bdist.linux-x86_64/wheel/django/apps copying build/lib/django/apps/__init__.py -> build/bdist.linux-x86_64/wheel/django/apps copying build/lib/django/apps/registry.py -> build/bdist.linux-x86_64/wheel/django/apps copying build/lib/django/apps/config.py -> build/bdist.linux-x86_64/wheel/django/apps creating build/bdist.linux-x86_64/wheel/django/db creating build/bdist.linux-x86_64/wheel/django/db/migrations creating build/bdist.linux-x86_64/wheel/django/db/migrations/operations copying build/lib/django/db/migrations/operations/special.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations copying build/lib/django/db/migrations/operations/fields.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations copying build/lib/django/db/migrations/operations/models.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations copying build/lib/django/db/migrations/operations/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations copying build/lib/django/db/migrations/operations/base.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations copying build/lib/django/db/migrations/autodetector.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/utils.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/serializer.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/exceptions.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/writer.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/executor.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/recorder.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/migration.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/state.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/questioner.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/loader.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/optimizer.py -> build/bdist.linux-x86_64/wheel/django/db/migrations copying build/lib/django/db/migrations/graph.py -> build/bdist.linux-x86_64/wheel/django/db/migrations creating build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/options.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/query_utils.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/signals.py -> build/bdist.linux-x86_64/wheel/django/db/models creating build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/related_descriptors.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/related_lookups.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/files.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/reverse_related.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/related.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/mixins.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/json.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/fields/proxy.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields copying build/lib/django/db/models/indexes.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/utils.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/constraints.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/expressions.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/deletion.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/query.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/aggregates.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/enums.py -> build/bdist.linux-x86_64/wheel/django/db/models creating build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/sql/query.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/sql/where.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/sql/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/sql/compiler.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/sql/subqueries.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/sql/constants.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/sql/datastructures.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql copying build/lib/django/db/models/base.py -> build/bdist.linux-x86_64/wheel/django/db/models creating build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/functions/text.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/functions/datetime.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/functions/math.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/functions/window.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/functions/comparison.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/functions/mixins.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/functions/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions copying build/lib/django/db/models/constants.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/lookups.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/models/manager.py -> build/bdist.linux-x86_64/wheel/django/db/models copying build/lib/django/db/transaction.py -> build/bdist.linux-x86_64/wheel/django/db creating build/bdist.linux-x86_64/wheel/django/db/backends creating build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/compiler.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql copying build/lib/django/db/backends/mysql/validation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql creating build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/_functions.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 copying build/lib/django/db/backends/sqlite3/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3 creating build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/validation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/base/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base copying build/lib/django/db/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends creating build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/validation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/functions.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/utils.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle copying build/lib/django/db/backends/oracle/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle creating build/bdist.linux-x86_64/wheel/django/db/backends/dummy copying build/lib/django/db/backends/dummy/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/dummy copying build/lib/django/db/backends/dummy/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/dummy copying build/lib/django/db/backends/dummy/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/dummy copying build/lib/django/db/backends/ddl_references.py -> build/bdist.linux-x86_64/wheel/django/db/backends copying build/lib/django/db/backends/utils.py -> build/bdist.linux-x86_64/wheel/django/db/backends creating build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/psycopg_any.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/postgresql/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql copying build/lib/django/db/backends/signals.py -> build/bdist.linux-x86_64/wheel/django/db/backends copying build/lib/django/db/__init__.py -> build/bdist.linux-x86_64/wheel/django/db copying build/lib/django/db/utils.py -> build/bdist.linux-x86_64/wheel/django/db creating build/bdist.linux-x86_64/wheel/django/dispatch copying build/lib/django/dispatch/license.txt -> build/bdist.linux-x86_64/wheel/django/dispatch copying build/lib/django/dispatch/dispatcher.py -> build/bdist.linux-x86_64/wheel/django/dispatch copying build/lib/django/dispatch/__init__.py -> build/bdist.linux-x86_64/wheel/django/dispatch copying build/lib/django/shortcuts.py -> build/bdist.linux-x86_64/wheel/django creating build/bdist.linux-x86_64/wheel/django/conf copying build/lib/django/conf/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf copying build/lib/django/conf/__init__.py.orig -> build/bdist.linux-x86_64/wheel/django/conf creating build/bdist.linux-x86_64/wheel/django/conf/app_template copying build/lib/django/conf/app_template/tests.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template copying build/lib/django/conf/app_template/admin.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template creating build/bdist.linux-x86_64/wheel/django/conf/app_template/migrations copying build/lib/django/conf/app_template/migrations/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template/migrations copying build/lib/django/conf/app_template/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template copying build/lib/django/conf/app_template/views.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template copying build/lib/django/conf/app_template/models.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template copying build/lib/django/conf/app_template/apps.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template creating build/bdist.linux-x86_64/wheel/django/conf/project_template copying build/lib/django/conf/project_template/manage.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template creating build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/asgi.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/urls.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/settings.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name copying build/lib/django/conf/project_template/project_name/wsgi.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name creating build/bdist.linux-x86_64/wheel/django/conf/urls copying build/lib/django/conf/urls/static.py -> build/bdist.linux-x86_64/wheel/django/conf/urls copying build/lib/django/conf/urls/i18n.py -> build/bdist.linux-x86_64/wheel/django/conf/urls copying build/lib/django/conf/urls/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/urls creating build/bdist.linux-x86_64/wheel/django/conf/locale creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE/LC_MESSAGES copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE/LC_MESSAGES copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/nb copying build/lib/django/conf/locale/nb/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb creating build/bdist.linux-x86_64/wheel/django/conf/locale/nb/LC_MESSAGES copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb/LC_MESSAGES copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb/LC_MESSAGES copying build/lib/django/conf/locale/nb/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb creating build/bdist.linux-x86_64/wheel/django/conf/locale/io creating build/bdist.linux-x86_64/wheel/django/conf/locale/io/LC_MESSAGES copying build/lib/django/conf/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/io/LC_MESSAGES copying build/lib/django/conf/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ga copying build/lib/django/conf/locale/ga/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga creating build/bdist.linux-x86_64/wheel/django/conf/locale/ga/LC_MESSAGES copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga/LC_MESSAGES copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga/LC_MESSAGES copying build/lib/django/conf/locale/ga/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga creating build/bdist.linux-x86_64/wheel/django/conf/locale/bg copying build/lib/django/conf/locale/bg/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg copying build/lib/django/conf/locale/bg/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg creating build/bdist.linux-x86_64/wheel/django/conf/locale/bg/LC_MESSAGES copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg/LC_MESSAGES copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/kn creating build/bdist.linux-x86_64/wheel/django/conf/locale/kn/LC_MESSAGES copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn/LC_MESSAGES copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn/LC_MESSAGES copying build/lib/django/conf/locale/kn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn copying build/lib/django/conf/locale/kn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn creating build/bdist.linux-x86_64/wheel/django/conf/locale/pa creating build/bdist.linux-x86_64/wheel/django/conf/locale/pa/LC_MESSAGES copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pa/LC_MESSAGES copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/et copying build/lib/django/conf/locale/et/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/et copying build/lib/django/conf/locale/et/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/et creating build/bdist.linux-x86_64/wheel/django/conf/locale/et/LC_MESSAGES copying build/lib/django/conf/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/et/LC_MESSAGES copying build/lib/django/conf/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/bs copying build/lib/django/conf/locale/bs/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs copying build/lib/django/conf/locale/bs/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs creating build/bdist.linux-x86_64/wheel/django/conf/locale/bs/LC_MESSAGES copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs/LC_MESSAGES copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/udm creating build/bdist.linux-x86_64/wheel/django/conf/locale/udm/LC_MESSAGES copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/udm/LC_MESSAGES copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/sw creating build/bdist.linux-x86_64/wheel/django/conf/locale/sw/LC_MESSAGES copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sw/LC_MESSAGES copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ast creating build/bdist.linux-x86_64/wheel/django/conf/locale/ast/LC_MESSAGES copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ast/LC_MESSAGES copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/hr copying build/lib/django/conf/locale/hr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr creating build/bdist.linux-x86_64/wheel/django/conf/locale/hr/LC_MESSAGES copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr/LC_MESSAGES copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr/LC_MESSAGES copying build/lib/django/conf/locale/hr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr creating build/bdist.linux-x86_64/wheel/django/conf/locale/hu copying build/lib/django/conf/locale/hu/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu creating build/bdist.linux-x86_64/wheel/django/conf/locale/hu/LC_MESSAGES copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu/LC_MESSAGES copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu/LC_MESSAGES copying build/lib/django/conf/locale/hu/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu creating build/bdist.linux-x86_64/wheel/django/conf/locale/pl creating build/bdist.linux-x86_64/wheel/django/conf/locale/pl/LC_MESSAGES copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl/LC_MESSAGES copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl/LC_MESSAGES copying build/lib/django/conf/locale/pl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl copying build/lib/django/conf/locale/pl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl creating build/bdist.linux-x86_64/wheel/django/conf/locale/dsb creating build/bdist.linux-x86_64/wheel/django/conf/locale/dsb/LC_MESSAGES copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/dsb/LC_MESSAGES copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/es creating build/bdist.linux-x86_64/wheel/django/conf/locale/es/LC_MESSAGES copying build/lib/django/conf/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es/LC_MESSAGES copying build/lib/django/conf/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es/LC_MESSAGES copying build/lib/django/conf/locale/es/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es copying build/lib/django/conf/locale/es/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_PR copying build/lib/django/conf/locale/es_PR/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_PR copying build/lib/django/conf/locale/es_PR/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_PR creating build/bdist.linux-x86_64/wheel/django/conf/locale/gl copying build/lib/django/conf/locale/gl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl creating build/bdist.linux-x86_64/wheel/django/conf/locale/gl/LC_MESSAGES copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl/LC_MESSAGES copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl/LC_MESSAGES copying build/lib/django/conf/locale/gl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl creating build/bdist.linux-x86_64/wheel/django/conf/locale/ne creating build/bdist.linux-x86_64/wheel/django/conf/locale/ne/LC_MESSAGES copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ne/LC_MESSAGES copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ne/LC_MESSAGES copying build/lib/django/conf/locale/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale creating build/bdist.linux-x86_64/wheel/django/conf/locale/my creating build/bdist.linux-x86_64/wheel/django/conf/locale/my/LC_MESSAGES copying build/lib/django/conf/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/my/LC_MESSAGES copying build/lib/django/conf/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ms copying build/lib/django/conf/locale/ms/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms copying build/lib/django/conf/locale/ms/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms creating build/bdist.linux-x86_64/wheel/django/conf/locale/ms/LC_MESSAGES copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms/LC_MESSAGES copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/cy creating build/bdist.linux-x86_64/wheel/django/conf/locale/cy/LC_MESSAGES copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy/LC_MESSAGES copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy/LC_MESSAGES copying build/lib/django/conf/locale/cy/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy copying build/lib/django/conf/locale/cy/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy creating build/bdist.linux-x86_64/wheel/django/conf/locale/cs copying build/lib/django/conf/locale/cs/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs copying build/lib/django/conf/locale/cs/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs creating build/bdist.linux-x86_64/wheel/django/conf/locale/cs/LC_MESSAGES copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs/LC_MESSAGES copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/uz copying build/lib/django/conf/locale/uz/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz copying build/lib/django/conf/locale/uz/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz creating build/bdist.linux-x86_64/wheel/django/conf/locale/uz/LC_MESSAGES copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz/LC_MESSAGES copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ky creating build/bdist.linux-x86_64/wheel/django/conf/locale/ky/LC_MESSAGES copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky/LC_MESSAGES copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky/LC_MESSAGES copying build/lib/django/conf/locale/ky/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky copying build/lib/django/conf/locale/ky/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky creating build/bdist.linux-x86_64/wheel/django/conf/locale/lt creating build/bdist.linux-x86_64/wheel/django/conf/locale/lt/LC_MESSAGES copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt/LC_MESSAGES copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt/LC_MESSAGES copying build/lib/django/conf/locale/lt/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt copying build/lib/django/conf/locale/lt/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt creating build/bdist.linux-x86_64/wheel/django/conf/locale/bn copying build/lib/django/conf/locale/bn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn creating build/bdist.linux-x86_64/wheel/django/conf/locale/bn/LC_MESSAGES copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn/LC_MESSAGES copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn/LC_MESSAGES copying build/lib/django/conf/locale/bn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn creating build/bdist.linux-x86_64/wheel/django/conf/locale/km copying build/lib/django/conf/locale/km/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/km copying build/lib/django/conf/locale/km/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/km creating build/bdist.linux-x86_64/wheel/django/conf/locale/km/LC_MESSAGES copying build/lib/django/conf/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/km/LC_MESSAGES copying build/lib/django/conf/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR copying build/lib/django/conf/locale/es_AR/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR/LC_MESSAGES copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR/LC_MESSAGES copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR/LC_MESSAGES copying build/lib/django/conf/locale/es_AR/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/conf/locale/tg copying build/lib/django/conf/locale/tg/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg creating build/bdist.linux-x86_64/wheel/django/conf/locale/tg/LC_MESSAGES copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg/LC_MESSAGES copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg/LC_MESSAGES copying build/lib/django/conf/locale/tg/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar/LC_MESSAGES copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar/LC_MESSAGES copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar/LC_MESSAGES copying build/lib/django/conf/locale/ar/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar copying build/lib/django/conf/locale/ar/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar creating build/bdist.linux-x86_64/wheel/django/conf/locale/he creating build/bdist.linux-x86_64/wheel/django/conf/locale/he/LC_MESSAGES copying build/lib/django/conf/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/he/LC_MESSAGES copying build/lib/django/conf/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/he/LC_MESSAGES copying build/lib/django/conf/locale/he/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/he copying build/lib/django/conf/locale/he/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/he creating build/bdist.linux-x86_64/wheel/django/conf/locale/fa copying build/lib/django/conf/locale/fa/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa copying build/lib/django/conf/locale/fa/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa creating build/bdist.linux-x86_64/wheel/django/conf/locale/fa/LC_MESSAGES copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa/LC_MESSAGES copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/af creating build/bdist.linux-x86_64/wheel/django/conf/locale/af/LC_MESSAGES copying build/lib/django/conf/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/af/LC_MESSAGES copying build/lib/django/conf/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn copying build/lib/django/conf/locale/sr_Latn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES copying build/lib/django/conf/locale/sr_Latn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/conf/locale/tt creating build/bdist.linux-x86_64/wheel/django/conf/locale/tt/LC_MESSAGES copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tt/LC_MESSAGES copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/fr copying build/lib/django/conf/locale/fr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr copying build/lib/django/conf/locale/fr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr creating build/bdist.linux-x86_64/wheel/django/conf/locale/fr/LC_MESSAGES copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr/LC_MESSAGES copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/en copying build/lib/django/conf/locale/en/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en copying build/lib/django/conf/locale/en/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en creating build/bdist.linux-x86_64/wheel/django/conf/locale/en/LC_MESSAGES copying build/lib/django/conf/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/en/LC_MESSAGES copying build/lib/django/conf/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/nl copying build/lib/django/conf/locale/nl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl creating build/bdist.linux-x86_64/wheel/django/conf/locale/nl/LC_MESSAGES copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl/LC_MESSAGES copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl/LC_MESSAGES copying build/lib/django/conf/locale/nl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl creating build/bdist.linux-x86_64/wheel/django/conf/locale/ia creating build/bdist.linux-x86_64/wheel/django/conf/locale/ia/LC_MESSAGES copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ia/LC_MESSAGES copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/kab creating build/bdist.linux-x86_64/wheel/django/conf/locale/kab/LC_MESSAGES copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/kab/LC_MESSAGES copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/kab/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/mn copying build/lib/django/conf/locale/mn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn copying build/lib/django/conf/locale/mn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn creating build/bdist.linux-x86_64/wheel/django/conf/locale/mn/LC_MESSAGES copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn/LC_MESSAGES copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/uk creating build/bdist.linux-x86_64/wheel/django/conf/locale/uk/LC_MESSAGES copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk/LC_MESSAGES copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk/LC_MESSAGES copying build/lib/django/conf/locale/uk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk copying build/lib/django/conf/locale/uk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB copying build/lib/django/conf/locale/en_GB/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB copying build/lib/django/conf/locale/en_GB/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB/LC_MESSAGES copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB/LC_MESSAGES copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/nn copying build/lib/django/conf/locale/nn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn creating build/bdist.linux-x86_64/wheel/django/conf/locale/nn/LC_MESSAGES copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn/LC_MESSAGES copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn/LC_MESSAGES copying build/lib/django/conf/locale/nn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn creating build/bdist.linux-x86_64/wheel/django/conf/locale/vi copying build/lib/django/conf/locale/vi/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi creating build/bdist.linux-x86_64/wheel/django/conf/locale/vi/LC_MESSAGES copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi/LC_MESSAGES copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi/LC_MESSAGES copying build/lib/django/conf/locale/vi/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi creating build/bdist.linux-x86_64/wheel/django/conf/locale/mr creating build/bdist.linux-x86_64/wheel/django/conf/locale/mr/LC_MESSAGES copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/mr/LC_MESSAGES copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX/LC_MESSAGES copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX/LC_MESSAGES copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX/LC_MESSAGES copying build/lib/django/conf/locale/es_MX/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX copying build/lib/django/conf/locale/es_MX/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/conf/locale/de creating build/bdist.linux-x86_64/wheel/django/conf/locale/de/LC_MESSAGES copying build/lib/django/conf/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/de/LC_MESSAGES copying build/lib/django/conf/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/de/LC_MESSAGES copying build/lib/django/conf/locale/de/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de copying build/lib/django/conf/locale/de/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de creating build/bdist.linux-x86_64/wheel/django/conf/locale/ml creating build/bdist.linux-x86_64/wheel/django/conf/locale/ml/LC_MESSAGES copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml/LC_MESSAGES copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml/LC_MESSAGES copying build/lib/django/conf/locale/ml/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml copying build/lib/django/conf/locale/ml/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml creating build/bdist.linux-x86_64/wheel/django/conf/locale/ja copying build/lib/django/conf/locale/ja/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja creating build/bdist.linux-x86_64/wheel/django/conf/locale/ja/LC_MESSAGES copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja/LC_MESSAGES copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja/LC_MESSAGES copying build/lib/django/conf/locale/ja/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja creating build/bdist.linux-x86_64/wheel/django/conf/locale/os creating build/bdist.linux-x86_64/wheel/django/conf/locale/os/LC_MESSAGES copying build/lib/django/conf/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/os/LC_MESSAGES copying build/lib/django/conf/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/th copying build/lib/django/conf/locale/th/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/th creating build/bdist.linux-x86_64/wheel/django/conf/locale/th/LC_MESSAGES copying build/lib/django/conf/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/th/LC_MESSAGES copying build/lib/django/conf/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/th/LC_MESSAGES copying build/lib/django/conf/locale/th/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/th creating build/bdist.linux-x86_64/wheel/django/conf/locale/sq copying build/lib/django/conf/locale/sq/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq creating build/bdist.linux-x86_64/wheel/django/conf/locale/sq/LC_MESSAGES copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq/LC_MESSAGES copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq/LC_MESSAGES copying build/lib/django/conf/locale/sq/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq creating build/bdist.linux-x86_64/wheel/django/conf/locale/el creating build/bdist.linux-x86_64/wheel/django/conf/locale/el/LC_MESSAGES copying build/lib/django/conf/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/el/LC_MESSAGES copying build/lib/django/conf/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/el/LC_MESSAGES copying build/lib/django/conf/locale/el/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/el copying build/lib/django/conf/locale/el/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/el creating build/bdist.linux-x86_64/wheel/django/conf/locale/lb creating build/bdist.linux-x86_64/wheel/django/conf/locale/lb/LC_MESSAGES copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/lb/LC_MESSAGES copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt copying build/lib/django/conf/locale/pt/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt/LC_MESSAGES copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt/LC_MESSAGES copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt/LC_MESSAGES copying build/lib/django/conf/locale/pt/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt creating build/bdist.linux-x86_64/wheel/django/conf/locale/ko creating build/bdist.linux-x86_64/wheel/django/conf/locale/ko/LC_MESSAGES copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko/LC_MESSAGES copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko/LC_MESSAGES copying build/lib/django/conf/locale/ko/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko copying build/lib/django/conf/locale/ko/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko creating build/bdist.linux-x86_64/wheel/django/conf/locale/br creating build/bdist.linux-x86_64/wheel/django/conf/locale/br/LC_MESSAGES copying build/lib/django/conf/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/br/LC_MESSAGES copying build/lib/django/conf/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/eu copying build/lib/django/conf/locale/eu/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu creating build/bdist.linux-x86_64/wheel/django/conf/locale/eu/LC_MESSAGES copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu/LC_MESSAGES copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu/LC_MESSAGES copying build/lib/django/conf/locale/eu/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu creating build/bdist.linux-x86_64/wheel/django/conf/locale/lv copying build/lib/django/conf/locale/lv/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv copying build/lib/django/conf/locale/lv/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv creating build/bdist.linux-x86_64/wheel/django/conf/locale/lv/LC_MESSAGES copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv/LC_MESSAGES copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ckb copying build/lib/django/conf/locale/ckb/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb copying build/lib/django/conf/locale/ckb/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb creating build/bdist.linux-x86_64/wheel/django/conf/locale/ckb/LC_MESSAGES copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb/LC_MESSAGES copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/fi copying build/lib/django/conf/locale/fi/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi copying build/lib/django/conf/locale/fi/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi creating build/bdist.linux-x86_64/wheel/django/conf/locale/fi/LC_MESSAGES copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi/LC_MESSAGES copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/sv creating build/bdist.linux-x86_64/wheel/django/conf/locale/sv/LC_MESSAGES copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv/LC_MESSAGES copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv/LC_MESSAGES copying build/lib/django/conf/locale/sv/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv copying build/lib/django/conf/locale/sv/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv creating build/bdist.linux-x86_64/wheel/django/conf/locale/hy creating build/bdist.linux-x86_64/wheel/django/conf/locale/hy/LC_MESSAGES copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hy/LC_MESSAGES copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/te copying build/lib/django/conf/locale/te/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/te copying build/lib/django/conf/locale/te/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/te creating build/bdist.linux-x86_64/wheel/django/conf/locale/te/LC_MESSAGES copying build/lib/django/conf/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/te/LC_MESSAGES copying build/lib/django/conf/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU copying build/lib/django/conf/locale/en_AU/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU/LC_MESSAGES copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU/LC_MESSAGES copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU/LC_MESSAGES copying build/lib/django/conf/locale/en_AU/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/conf/locale/az copying build/lib/django/conf/locale/az/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/az creating build/bdist.linux-x86_64/wheel/django/conf/locale/az/LC_MESSAGES copying build/lib/django/conf/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/az/LC_MESSAGES copying build/lib/django/conf/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/az/LC_MESSAGES copying build/lib/django/conf/locale/az/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/az creating build/bdist.linux-x86_64/wheel/django/conf/locale/mk copying build/lib/django/conf/locale/mk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk copying build/lib/django/conf/locale/mk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk creating build/bdist.linux-x86_64/wheel/django/conf/locale/mk/LC_MESSAGES copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk/LC_MESSAGES copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO/LC_MESSAGES copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO/LC_MESSAGES copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO/LC_MESSAGES copying build/lib/django/conf/locale/es_CO/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO copying build/lib/django/conf/locale/es_CO/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/conf/locale/ur creating build/bdist.linux-x86_64/wheel/django/conf/locale/ur/LC_MESSAGES copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ur/LC_MESSAGES copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ru creating build/bdist.linux-x86_64/wheel/django/conf/locale/ru/LC_MESSAGES copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru/LC_MESSAGES copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru/LC_MESSAGES copying build/lib/django/conf/locale/ru/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru copying build/lib/django/conf/locale/ru/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_NI copying build/lib/django/conf/locale/es_NI/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_NI copying build/lib/django/conf/locale/es_NI/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_NI creating build/bdist.linux-x86_64/wheel/django/conf/locale/id copying build/lib/django/conf/locale/id/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/id creating build/bdist.linux-x86_64/wheel/django/conf/locale/id/LC_MESSAGES copying build/lib/django/conf/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/id/LC_MESSAGES copying build/lib/django/conf/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/id/LC_MESSAGES copying build/lib/django/conf/locale/id/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/id creating build/bdist.linux-x86_64/wheel/django/conf/locale/hsb creating build/bdist.linux-x86_64/wheel/django/conf/locale/hsb/LC_MESSAGES copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hsb/LC_MESSAGES copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/gd copying build/lib/django/conf/locale/gd/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd creating build/bdist.linux-x86_64/wheel/django/conf/locale/gd/LC_MESSAGES copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd/LC_MESSAGES copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd/LC_MESSAGES copying build/lib/django/conf/locale/gd/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES copying build/lib/django/conf/locale/ar_DZ/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ copying build/lib/django/conf/locale/ar_DZ/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/conf/locale/ro creating build/bdist.linux-x86_64/wheel/django/conf/locale/ro/LC_MESSAGES copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro/LC_MESSAGES copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro/LC_MESSAGES copying build/lib/django/conf/locale/ro/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro copying build/lib/django/conf/locale/ro/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro creating build/bdist.linux-x86_64/wheel/django/conf/locale/it copying build/lib/django/conf/locale/it/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/it copying build/lib/django/conf/locale/it/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/it creating build/bdist.linux-x86_64/wheel/django/conf/locale/it/LC_MESSAGES copying build/lib/django/conf/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/it/LC_MESSAGES copying build/lib/django/conf/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ca creating build/bdist.linux-x86_64/wheel/django/conf/locale/ca/LC_MESSAGES copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca/LC_MESSAGES copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca/LC_MESSAGES copying build/lib/django/conf/locale/ca/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca copying build/lib/django/conf/locale/ca/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant copying build/lib/django/conf/locale/zh_Hant/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hant/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr/LC_MESSAGES copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr/LC_MESSAGES copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr/LC_MESSAGES copying build/lib/django/conf/locale/sr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr copying build/lib/django/conf/locale/sr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr creating build/bdist.linux-x86_64/wheel/django/conf/locale/hi copying build/lib/django/conf/locale/hi/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi copying build/lib/django/conf/locale/hi/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi creating build/bdist.linux-x86_64/wheel/django/conf/locale/hi/LC_MESSAGES copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi/LC_MESSAGES copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/de_CH copying build/lib/django/conf/locale/de_CH/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de_CH copying build/lib/django/conf/locale/de_CH/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de_CH creating build/bdist.linux-x86_64/wheel/django/conf/locale/sl copying build/lib/django/conf/locale/sl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl creating build/bdist.linux-x86_64/wheel/django/conf/locale/sl/LC_MESSAGES copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl/LC_MESSAGES copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl/LC_MESSAGES copying build/lib/django/conf/locale/sl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl creating build/bdist.linux-x86_64/wheel/django/conf/locale/tk creating build/bdist.linux-x86_64/wheel/django/conf/locale/tk/LC_MESSAGES copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk/LC_MESSAGES copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk/LC_MESSAGES copying build/lib/django/conf/locale/tk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk copying build/lib/django/conf/locale/tk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk creating build/bdist.linux-x86_64/wheel/django/conf/locale/fy creating build/bdist.linux-x86_64/wheel/django/conf/locale/fy/LC_MESSAGES copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy/LC_MESSAGES copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy/LC_MESSAGES copying build/lib/django/conf/locale/fy/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy copying build/lib/django/conf/locale/fy/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy creating build/bdist.linux-x86_64/wheel/django/conf/locale/ta copying build/lib/django/conf/locale/ta/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta copying build/lib/django/conf/locale/ta/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta creating build/bdist.linux-x86_64/wheel/django/conf/locale/ta/LC_MESSAGES copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta/LC_MESSAGES copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/kk creating build/bdist.linux-x86_64/wheel/django/conf/locale/kk/LC_MESSAGES copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/kk/LC_MESSAGES copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/ka creating build/bdist.linux-x86_64/wheel/django/conf/locale/ka/LC_MESSAGES copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka/LC_MESSAGES copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka/LC_MESSAGES copying build/lib/django/conf/locale/ka/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka copying build/lib/django/conf/locale/ka/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka creating build/bdist.linux-x86_64/wheel/django/conf/locale/eo creating build/bdist.linux-x86_64/wheel/django/conf/locale/eo/LC_MESSAGES copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo/LC_MESSAGES copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo/LC_MESSAGES copying build/lib/django/conf/locale/eo/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo copying build/lib/django/conf/locale/eo/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo creating build/bdist.linux-x86_64/wheel/django/conf/locale/be creating build/bdist.linux-x86_64/wheel/django/conf/locale/be/LC_MESSAGES copying build/lib/django/conf/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/be/LC_MESSAGES copying build/lib/django/conf/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR/LC_MESSAGES copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR/LC_MESSAGES copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR/LC_MESSAGES copying build/lib/django/conf/locale/pt_BR/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR copying build/lib/django/conf/locale/pt_BR/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/conf/locale/sk copying build/lib/django/conf/locale/sk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk creating build/bdist.linux-x86_64/wheel/django/conf/locale/sk/LC_MESSAGES copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk/LC_MESSAGES copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk/LC_MESSAGES copying build/lib/django/conf/locale/sk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans copying build/lib/django/conf/locale/zh_Hans/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES copying build/lib/django/conf/locale/zh_Hans/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/conf/locale/tr copying build/lib/django/conf/locale/tr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr creating build/bdist.linux-x86_64/wheel/django/conf/locale/tr/LC_MESSAGES copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr/LC_MESSAGES copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr/LC_MESSAGES copying build/lib/django/conf/locale/tr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr creating build/bdist.linux-x86_64/wheel/django/conf/locale/da creating build/bdist.linux-x86_64/wheel/django/conf/locale/da/LC_MESSAGES copying build/lib/django/conf/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/da/LC_MESSAGES copying build/lib/django/conf/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/da/LC_MESSAGES copying build/lib/django/conf/locale/da/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/da copying build/lib/django/conf/locale/da/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/da creating build/bdist.linux-x86_64/wheel/django/conf/locale/is creating build/bdist.linux-x86_64/wheel/django/conf/locale/is/LC_MESSAGES copying build/lib/django/conf/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/is/LC_MESSAGES copying build/lib/django/conf/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/is/LC_MESSAGES copying build/lib/django/conf/locale/is/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/is copying build/lib/django/conf/locale/is/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/is creating build/bdist.linux-x86_64/wheel/django/conf/locale/ig creating build/bdist.linux-x86_64/wheel/django/conf/locale/ig/LC_MESSAGES copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig/LC_MESSAGES copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig/LC_MESSAGES copying build/lib/django/conf/locale/ig/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig copying build/lib/django/conf/locale/ig/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig copying build/lib/django/conf/global_settings.py -> build/bdist.linux-x86_64/wheel/django/conf creating build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/archive.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/regex_helper.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/module_loading.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/formats.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/duration.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/jslex.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/autoreload.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/encoding.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/_os.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/cache.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/http.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/datastructures.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/log.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/deconstruct.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/html.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/itercompat.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/ipv6.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/hashable.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/text.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/connection.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/crypto.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/lorem_ipsum.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/functional.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/asyncio.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/dateformat.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/xmlutils.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/deprecation.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/numberformat.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/dates.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/datetime_safe.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/tree.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/termcolors.py -> build/bdist.linux-x86_64/wheel/django/utils creating build/bdist.linux-x86_64/wheel/django/utils/translation copying build/lib/django/utils/translation/trans_null.py -> build/bdist.linux-x86_64/wheel/django/utils/translation copying build/lib/django/utils/translation/template.py -> build/bdist.linux-x86_64/wheel/django/utils/translation copying build/lib/django/utils/translation/__init__.py -> build/bdist.linux-x86_64/wheel/django/utils/translation copying build/lib/django/utils/translation/trans_real.py -> build/bdist.linux-x86_64/wheel/django/utils/translation copying build/lib/django/utils/translation/reloader.py -> build/bdist.linux-x86_64/wheel/django/utils/translation copying build/lib/django/utils/version.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/baseconv.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/timesince.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/__init__.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/topological_sort.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/timezone.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/decorators.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/inspect.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/feedgenerator.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/dateparse.py -> build/bdist.linux-x86_64/wheel/django/utils copying build/lib/django/utils/safestring.py -> build/bdist.linux-x86_64/wheel/django/utils creating build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/utils.py -> build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/__init__.py -> build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/html.py -> build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/client.py -> build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/signals.py -> build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/runner.py -> build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/selenium.py -> build/bdist.linux-x86_64/wheel/django/test copying build/lib/django/test/testcases.py -> build/bdist.linux-x86_64/wheel/django/test creating build/bdist.linux-x86_64/wheel/django/templatetags copying build/lib/django/templatetags/tz.py -> build/bdist.linux-x86_64/wheel/django/templatetags copying build/lib/django/templatetags/i18n.py -> build/bdist.linux-x86_64/wheel/django/templatetags copying build/lib/django/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/templatetags copying build/lib/django/templatetags/cache.py -> build/bdist.linux-x86_64/wheel/django/templatetags copying build/lib/django/templatetags/static.py -> build/bdist.linux-x86_64/wheel/django/templatetags copying build/lib/django/templatetags/l10n.py -> build/bdist.linux-x86_64/wheel/django/templatetags creating build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/engine.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/autoreload.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/utils.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/loader_tags.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/defaultfilters.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/__init__.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/context.py -> build/bdist.linux-x86_64/wheel/django/template creating build/bdist.linux-x86_64/wheel/django/template/backends copying build/lib/django/template/backends/utils.py -> build/bdist.linux-x86_64/wheel/django/template/backends copying build/lib/django/template/backends/jinja2.py -> build/bdist.linux-x86_64/wheel/django/template/backends copying build/lib/django/template/backends/dummy.py -> build/bdist.linux-x86_64/wheel/django/template/backends copying build/lib/django/template/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/template/backends copying build/lib/django/template/backends/django.py -> build/bdist.linux-x86_64/wheel/django/template/backends copying build/lib/django/template/backends/base.py -> build/bdist.linux-x86_64/wheel/django/template/backends copying build/lib/django/template/response.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/defaulttags.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/loader.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/smartif.py -> build/bdist.linux-x86_64/wheel/django/template creating build/bdist.linux-x86_64/wheel/django/template/loaders copying build/lib/django/template/loaders/app_directories.py -> build/bdist.linux-x86_64/wheel/django/template/loaders copying build/lib/django/template/loaders/locmem.py -> build/bdist.linux-x86_64/wheel/django/template/loaders copying build/lib/django/template/loaders/base.py -> build/bdist.linux-x86_64/wheel/django/template/loaders copying build/lib/django/template/loaders/__init__.py -> build/bdist.linux-x86_64/wheel/django/template/loaders copying build/lib/django/template/loaders/filesystem.py -> build/bdist.linux-x86_64/wheel/django/template/loaders copying build/lib/django/template/loaders/cached.py -> build/bdist.linux-x86_64/wheel/django/template/loaders copying build/lib/django/template/library.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/exceptions.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/context_processors.py -> build/bdist.linux-x86_64/wheel/django/template copying build/lib/django/template/base.py -> build/bdist.linux-x86_64/wheel/django/template creating build/bdist.linux-x86_64/wheel/django/http copying build/lib/django/http/multipartparser.py -> build/bdist.linux-x86_64/wheel/django/http copying build/lib/django/http/request.py -> build/bdist.linux-x86_64/wheel/django/http copying build/lib/django/http/cookie.py -> build/bdist.linux-x86_64/wheel/django/http copying build/lib/django/http/__init__.py -> build/bdist.linux-x86_64/wheel/django/http copying build/lib/django/http/response.py -> build/bdist.linux-x86_64/wheel/django/http copying build/lib/django/__main__.py -> build/bdist.linux-x86_64/wheel/django creating build/bdist.linux-x86_64/wheel/django/views creating build/bdist.linux-x86_64/wheel/django/views/generic copying build/lib/django/views/generic/__init__.py -> build/bdist.linux-x86_64/wheel/django/views/generic copying build/lib/django/views/generic/base.py -> build/bdist.linux-x86_64/wheel/django/views/generic copying build/lib/django/views/generic/list.py -> build/bdist.linux-x86_64/wheel/django/views/generic copying build/lib/django/views/generic/detail.py -> build/bdist.linux-x86_64/wheel/django/views/generic copying build/lib/django/views/generic/edit.py -> build/bdist.linux-x86_64/wheel/django/views/generic copying build/lib/django/views/generic/dates.py -> build/bdist.linux-x86_64/wheel/django/views/generic copying build/lib/django/views/csrf.py -> build/bdist.linux-x86_64/wheel/django/views creating build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/__init__.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/cache.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/clickjacking.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/debug.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/gzip.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/http.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/csrf.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/common.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/decorators/vary.py -> build/bdist.linux-x86_64/wheel/django/views/decorators copying build/lib/django/views/i18n.py -> build/bdist.linux-x86_64/wheel/django/views copying build/lib/django/views/static.py -> build/bdist.linux-x86_64/wheel/django/views copying build/lib/django/views/debug.py -> build/bdist.linux-x86_64/wheel/django/views copying build/lib/django/views/__init__.py -> build/bdist.linux-x86_64/wheel/django/views copying build/lib/django/views/defaults.py -> build/bdist.linux-x86_64/wheel/django/views creating build/bdist.linux-x86_64/wheel/django/views/templates copying build/lib/django/views/templates/technical_500.html -> build/bdist.linux-x86_64/wheel/django/views/templates copying build/lib/django/views/templates/default_urlconf.html -> build/bdist.linux-x86_64/wheel/django/views/templates copying build/lib/django/views/templates/technical_404.html -> build/bdist.linux-x86_64/wheel/django/views/templates copying build/lib/django/views/templates/technical_500.txt -> build/bdist.linux-x86_64/wheel/django/views/templates creating build/bdist.linux-x86_64/wheel/django/urls copying build/lib/django/urls/conf.py -> build/bdist.linux-x86_64/wheel/django/urls copying build/lib/django/urls/exceptions.py -> build/bdist.linux-x86_64/wheel/django/urls copying build/lib/django/urls/converters.py -> build/bdist.linux-x86_64/wheel/django/urls copying build/lib/django/urls/resolvers.py -> build/bdist.linux-x86_64/wheel/django/urls copying build/lib/django/urls/__init__.py -> build/bdist.linux-x86_64/wheel/django/urls copying build/lib/django/urls/utils.py -> build/bdist.linux-x86_64/wheel/django/urls copying build/lib/django/urls/base.py -> build/bdist.linux-x86_64/wheel/django/urls creating build/bdist.linux-x86_64/wheel/django/forms copying build/lib/django/forms/models.py -> build/bdist.linux-x86_64/wheel/django/forms creating build/bdist.linux-x86_64/wheel/django/forms/templates creating build/bdist.linux-x86_64/wheel/django/forms/templates/django creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list copying build/lib/django/forms/templates/django/forms/errors/list/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list copying build/lib/django/forms/templates/django/forms/errors/list/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list copying build/lib/django/forms/templates/django/forms/errors/list/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict copying build/lib/django/forms/templates/django/forms/errors/dict/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict copying build/lib/django/forms/templates/django/forms/errors/dict/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict copying build/lib/django/forms/templates/django/forms/errors/dict/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/div.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/p.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/formsets/table.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets copying build/lib/django/forms/templates/django/forms/label.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/div.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/p.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/table.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms copying build/lib/django/forms/templates/django/forms/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/datetime.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/select_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/textarea.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/multiple_input.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/time.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/checkbox_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/radio_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/input.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/input_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/select_date.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/multiwidget.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/checkbox_select.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/splitdatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/date.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/checkbox.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/select.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/radio.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/password.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/file.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/number.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/url.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/text.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/templates/django/forms/widgets/email.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets copying build/lib/django/forms/forms.py -> build/bdist.linux-x86_64/wheel/django/forms creating build/bdist.linux-x86_64/wheel/django/forms/jinja2 creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list copying build/lib/django/forms/jinja2/django/forms/errors/list/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list copying build/lib/django/forms/jinja2/django/forms/errors/list/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list copying build/lib/django/forms/jinja2/django/forms/errors/list/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/errors/dict/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/errors/dict/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/errors/dict/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict copying build/lib/django/forms/jinja2/django/forms/label.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/div.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/p.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/table.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/input.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/time.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/datetime.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/textarea.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/select.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/date.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/select_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/url.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/password.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/select_date.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/radio_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/radio.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/input_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/file.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/text.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/number.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/email.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/div.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/table.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/p.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/formsets/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets copying build/lib/django/forms/jinja2/django/forms/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms copying build/lib/django/forms/jinja2/django/forms/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms copying build/lib/django/forms/widgets.py -> build/bdist.linux-x86_64/wheel/django/forms copying build/lib/django/forms/renderers.py -> build/bdist.linux-x86_64/wheel/django/forms copying build/lib/django/forms/formsets.py -> build/bdist.linux-x86_64/wheel/django/forms copying build/lib/django/forms/utils.py -> build/bdist.linux-x86_64/wheel/django/forms copying build/lib/django/forms/__init__.py -> build/bdist.linux-x86_64/wheel/django/forms copying build/lib/django/forms/boundfield.py -> build/bdist.linux-x86_64/wheel/django/forms copying build/lib/django/forms/fields.py -> build/bdist.linux-x86_64/wheel/django/forms creating build/bdist.linux-x86_64/wheel/django/contrib creating build/bdist.linux-x86_64/wheel/django/contrib/sessions creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/migrations copying build/lib/django/contrib/sessions/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/migrations copying build/lib/django/contrib/sessions/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/migrations copying build/lib/django/contrib/sessions/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions copying build/lib/django/contrib/sessions/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions copying build/lib/django/contrib/sessions/base_session.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions copying build/lib/django/contrib/sessions/serializers.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions copying build/lib/django/contrib/sessions/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions copying build/lib/django/contrib/sessions/exceptions.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/cached_db.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/signed_cookies.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/cache.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/db.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends copying build/lib/django/contrib/sessions/backends/file.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/management creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/management/commands copying build/lib/django/contrib/sessions/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/management/commands copying build/lib/django/contrib/sessions/management/commands/clearsessions.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/management/commands copying build/lib/django/contrib/sessions/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/management copying build/lib/django/contrib/sessions/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/expressions.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/constraints.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/hstore.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/array.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/forms/ranges.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms copying build/lib/django/contrib/postgres/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES copying build/lib/django/contrib/postgres/functions.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres/widgets copying build/lib/django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres/widgets copying build/lib/django/contrib/postgres/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/lookups.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/signals.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/search.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2 creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres/widgets copying build/lib/django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres/widgets copying build/lib/django/contrib/postgres/validators.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres copying build/lib/django/contrib/postgres/serializers.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/citext.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/array.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/ranges.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/jsonb.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/hstore.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/fields/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields copying build/lib/django/contrib/postgres/indexes.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/statistics.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/general.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates copying build/lib/django/contrib/postgres/aggregates/mixins.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates creating build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/sites.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/helpers.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/actions.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am/LC_MESSAGES copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am/LC_MESSAGES copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_change_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_email.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_complete.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_done.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_change_done.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/password_reset_confirm.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration copying build/lib/django/contrib/admin/templates/registration/logged_out.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth/user copying build/lib/django/contrib/admin/templates/admin/auth/user/change_password.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth/user copying build/lib/django/contrib/admin/templates/admin/auth/user/add_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth/user copying build/lib/django/contrib/admin/templates/admin/search_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/404.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/filter.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/change_list.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/delete_confirmation.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/login.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/change_list_results.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/popup_response.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/edit_inline copying build/lib/django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/edit_inline copying build/lib/django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/edit_inline copying build/lib/django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/change_form_object_tools.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/color_theme_toggle.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/submit_line.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/app_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/object_history.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/date_hierarchy.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/actions.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/includes copying build/lib/django/contrib/admin/templates/admin/includes/fieldset.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/includes copying build/lib/django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/includes copying build/lib/django/contrib/admin/templates/admin/index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/radio.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/time.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/date.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/widgets/url.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets copying build/lib/django/contrib/admin/templates/admin/change_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/500.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/app_list.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/pagination.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/base.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/invalid_setup.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/base_site.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/nav_sidebar.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin copying build/lib/django/contrib/admin/templates/admin/change_list_object_tools.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations copying build/lib/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations creating build/bdist.linux-x86_64/wheel/django/contrib/admin/views copying build/lib/django/contrib/admin/views/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views copying build/lib/django/contrib/admin/views/decorators.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views copying build/lib/django/contrib/admin/views/autocomplete.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views copying build/lib/django/contrib/admin/views/main.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/responsive.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/changelists.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/dark_mode.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/base.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2 copying build/lib/django/contrib/admin/static/admin/css/dashboard.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/nav_sidebar.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/autocomplete.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/forms.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/widgets.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/responsive_rtl.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/login.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css copying build/lib/django/contrib/admin/static/admin/css/rtl.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-unknown.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/README.txt -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-calendar.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/LICENSE -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/calendar-icons.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/search.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/inline-delete.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-clock.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/tooltag-add.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/sorting-icons.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-changelink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-alert.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-addlink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/selector-icons.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img copying build/lib/django/contrib/admin/static/admin/img/icon-yes.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img/gis copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img/gis copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img/gis copying build/lib/django/contrib/admin/static/admin/img/icon-no.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/calendar.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/theme.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/SelectFilter2.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/core.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/collapse.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/nav_sidebar.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/cancel.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/inlines.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/autocomplete.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/prepopulate_init.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2 copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2 copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2 copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2 creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp copying build/lib/django/contrib/admin/static/admin/js/filters.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/popup_response.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/admin copying build/lib/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/admin copying build/lib/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/admin copying build/lib/django/contrib/admin/static/admin/js/SelectBox.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/prepopulate.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/urlify.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/jquery.init.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/actions.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/static/admin/js/change_form.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js copying build/lib/django/contrib/admin/options.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/admin_urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/admin_modify.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/admin_list.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/log.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags copying build/lib/django/contrib/admin/filters.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/exceptions.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/decorators.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/tests.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin copying build/lib/django/contrib/admin/widgets.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin creating build/bdist.linux-x86_64/wheel/django/contrib/messages copying build/lib/django/contrib/messages/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages copying build/lib/django/contrib/messages/context_processors.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages copying build/lib/django/contrib/messages/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages copying build/lib/django/contrib/messages/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages copying build/lib/django/contrib/messages/api.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages copying build/lib/django/contrib/messages/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages copying build/lib/django/contrib/messages/constants.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages creating build/bdist.linux-x86_64/wheel/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/session.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/fallback.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage copying build/lib/django/contrib/messages/storage/cookie.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage copying build/lib/django/contrib/messages/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/templatetags copying build/lib/django/contrib/flatpages/templatetags/flatpages.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/templatetags copying build/lib/django/contrib/flatpages/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/templatetags copying build/lib/django/contrib/flatpages/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages copying build/lib/django/contrib/flatpages/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages copying build/lib/django/contrib/flatpages/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages copying build/lib/django/contrib/flatpages/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages copying build/lib/django/contrib/flatpages/sitemaps.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages copying build/lib/django/contrib/flatpages/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES copying build/lib/django/contrib/flatpages/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/migrations copying build/lib/django/contrib/flatpages/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/migrations copying build/lib/django/contrib/flatpages/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/migrations copying build/lib/django/contrib/flatpages/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages copying build/lib/django/contrib/flatpages/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages creating build/bdist.linux-x86_64/wheel/django/contrib/humanize copying build/lib/django/contrib/humanize/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize copying build/lib/django/contrib/humanize/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/templatetags copying build/lib/django/contrib/humanize/templatetags/humanize.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/templatetags copying build/lib/django/contrib/humanize/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/templatetags creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying build/lib/django/contrib/contenttypes/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations copying build/lib/django/contrib/contenttypes/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/fields.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes copying build/lib/django/contrib/contenttypes/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management copying build/lib/django/contrib/contenttypes/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management/commands copying build/lib/django/contrib/contenttypes/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management/commands copying build/lib/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management/commands copying build/lib/django/contrib/contenttypes/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes creating build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/tokens.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth creating build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations copying build/lib/django/contrib/auth/password_validation.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/common-passwords.txt.gz -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/validators.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/context_processors.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/base_user.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth creating build/bdist.linux-x86_64/wheel/django/contrib/auth/handlers copying build/lib/django/contrib/auth/handlers/modwsgi.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/handlers copying build/lib/django/contrib/auth/handlers/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/handlers copying build/lib/django/contrib/auth/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/registration copying build/lib/django/contrib/auth/templates/registration/password_reset_subject.txt -> build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/registration creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth/widgets copying build/lib/django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth/widgets copying build/lib/django/contrib/auth/decorators.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he/LC_MESSAGES copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he/LC_MESSAGES copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af/LC_MESSAGES copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af/LC_MESSAGES copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km/LC_MESSAGES copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km/LC_MESSAGES copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my/LC_MESSAGES copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my/LC_MESSAGES copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et/LC_MESSAGES copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et/LC_MESSAGES copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io/LC_MESSAGES copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io/LC_MESSAGES copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is/LC_MESSAGES copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is/LC_MESSAGES copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da/LC_MESSAGES copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da/LC_MESSAGES copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be/LC_MESSAGES copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be/LC_MESSAGES copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it/LC_MESSAGES copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it/LC_MESSAGES copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id/LC_MESSAGES copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id/LC_MESSAGES copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te/LC_MESSAGES copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te/LC_MESSAGES copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az/LC_MESSAGES copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az/LC_MESSAGES copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br/LC_MESSAGES copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br/LC_MESSAGES copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el/LC_MESSAGES copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el/LC_MESSAGES copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th/LC_MESSAGES copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th/LC_MESSAGES copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os/LC_MESSAGES copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os/LC_MESSAGES copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de/LC_MESSAGES copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de/LC_MESSAGES copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES copying build/lib/django/contrib/auth/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/mixins.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth creating build/bdist.linux-x86_64/wheel/django/contrib/auth/management copying build/lib/django/contrib/auth/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management creating build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/management/commands/changepassword.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/management/commands/createsuperuser.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands copying build/lib/django/contrib/auth/backends.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/hashers.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/signals.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth copying build/lib/django/contrib/auth/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth creating build/bdist.linux-x86_64/wheel/django/contrib/syndication copying build/lib/django/contrib/syndication/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/syndication copying build/lib/django/contrib/syndication/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/syndication copying build/lib/django/contrib/syndication/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/syndication creating build/bdist.linux-x86_64/wheel/django/contrib/redirects copying build/lib/django/contrib/redirects/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects copying build/lib/django/contrib/redirects/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects copying build/lib/django/contrib/redirects/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects copying build/lib/django/contrib/redirects/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations copying build/lib/django/contrib/redirects/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps copying build/lib/django/contrib/sitemaps/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/templates copying build/lib/django/contrib/sitemaps/templates/sitemap.xml -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/templates copying build/lib/django/contrib/sitemaps/templates/sitemap_index.xml -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/templates creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management copying build/lib/django/contrib/sitemaps/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management/commands copying build/lib/django/contrib/sitemaps/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management/commands copying build/lib/django/contrib/sitemaps/management/commands/ping_google.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management/commands copying build/lib/django/contrib/sitemaps/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps copying build/lib/django/contrib/sitemaps/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps creating build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/managers.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io/LC_MESSAGES copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io/LC_MESSAGES copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et/LC_MESSAGES copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et/LC_MESSAGES copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my/LC_MESSAGES copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my/LC_MESSAGES copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af/LC_MESSAGES copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af/LC_MESSAGES copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he/LC_MESSAGES copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he/LC_MESSAGES copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km/LC_MESSAGES copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km/LC_MESSAGES copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en/LC_MESSAGES copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de/LC_MESSAGES copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de/LC_MESSAGES copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el/LC_MESSAGES copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el/LC_MESSAGES copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os/LC_MESSAGES copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os/LC_MESSAGES copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th/LC_MESSAGES copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th/LC_MESSAGES copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az/LC_MESSAGES copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az/LC_MESSAGES copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te/LC_MESSAGES copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te/LC_MESSAGES copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br/LC_MESSAGES copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br/LC_MESSAGES copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id/LC_MESSAGES copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id/LC_MESSAGES copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it/LC_MESSAGES copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it/LC_MESSAGES copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be/LC_MESSAGES copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be/LC_MESSAGES copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is/LC_MESSAGES copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is/LC_MESSAGES copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da/LC_MESSAGES copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da/LC_MESSAGES copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da/LC_MESSAGES copying build/lib/django/contrib/sites/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites creating build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations copying build/lib/django/contrib/sites/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations copying build/lib/django/contrib/sites/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations copying build/lib/django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations copying build/lib/django/contrib/sites/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/management.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/shortcuts.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites copying build/lib/django/contrib/sites/requests.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites creating build/bdist.linux-x86_64/wheel/django/contrib/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/admin copying build/lib/django/contrib/gis/admin/widgets.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/admin copying build/lib/django/contrib/gis/admin/options.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/admin copying build/lib/django/contrib/gis/admin/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/admin creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/datasource.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/geomtype.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/srs.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/layer.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/ds.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/generation.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/raster.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/errcheck.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/srs.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/prototypes/geom.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes copying build/lib/django/contrib/gis/gdal/geometries.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/driver.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/field.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/source.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/const.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/raster/band.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster copying build/lib/django/contrib/gis/gdal/feature.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/libgdal.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/LICENSE -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/envelope.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/error.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/gdal/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal copying build/lib/django/contrib/gis/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis copying build/lib/django/contrib/gis/geometry.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/layermapping.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/srs.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/ogrinspect.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/ogrinfo.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils copying build/lib/django/contrib/gis/utils/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2 copying build/lib/django/contrib/gis/geoip2/resources.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2 copying build/lib/django/contrib/gis/geoip2/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2 copying build/lib/django/contrib/gis/geoip2/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2 creating build/bdist.linux-x86_64/wheel/django/contrib/gis/forms copying build/lib/django/contrib/gis/forms/widgets.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/forms copying build/lib/django/contrib/gis/forms/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/forms copying build/lib/django/contrib/gis/forms/fields.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/forms creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br/LC_MESSAGES copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br/LC_MESSAGES copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te/LC_MESSAGES copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te/LC_MESSAGES copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az/LC_MESSAGES copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az/LC_MESSAGES copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id/LC_MESSAGES copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id/LC_MESSAGES copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de/LC_MESSAGES copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de/LC_MESSAGES copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th/LC_MESSAGES copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th/LC_MESSAGES copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os/LC_MESSAGES copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os/LC_MESSAGES copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el/LC_MESSAGES copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el/LC_MESSAGES copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be/LC_MESSAGES copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be/LC_MESSAGES copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da/LC_MESSAGES copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da/LC_MESSAGES copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is/LC_MESSAGES copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is/LC_MESSAGES copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it/LC_MESSAGES copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it/LC_MESSAGES copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my/LC_MESSAGES copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my/LC_MESSAGES copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io/LC_MESSAGES copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io/LC_MESSAGES copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et/LC_MESSAGES copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et/LC_MESSAGES copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en/LC_MESSAGES copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km/LC_MESSAGES copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km/LC_MESSAGES copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he/LC_MESSAGES copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he/LC_MESSAGES copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af/LC_MESSAGES copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af/LC_MESSAGES copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/gis/serializers copying build/lib/django/contrib/gis/serializers/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/serializers copying build/lib/django/contrib/gis/serializers/geojson.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/serializers creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_line_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_point_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_line_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_point_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/js copying build/lib/django/contrib/gis/static/gis/js/OLMapWidget.js -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/js creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/css copying build/lib/django/contrib/gis/static/gis/css/ol3.css -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/css copying build/lib/django/contrib/gis/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/management creating build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/commands/ogrinspect.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/commands/inspectdb.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands copying build/lib/django/contrib/gis/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.js -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin copying build/lib/django/contrib/gis/templates/gis/admin/osm.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin copying build/lib/django/contrib/gis/templates/gis/admin/osm.js -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/kml copying build/lib/django/contrib/gis/templates/gis/kml/placemarks.kml -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/kml copying build/lib/django/contrib/gis/templates/gis/kml/base.kml -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/kml copying build/lib/django/contrib/gis/templates/gis/openlayers.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis copying build/lib/django/contrib/gis/templates/gis/openlayers-osm.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/functions.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/fields.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models/sql copying build/lib/django/contrib/gis/db/models/sql/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models/sql copying build/lib/django/contrib/gis/db/models/sql/conversion.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models/sql copying build/lib/django/contrib/gis/db/models/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/lookups.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/proxy.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/models/aggregates.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models copying build/lib/django/contrib/gis/db/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/const.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/pgraster.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis copying build/lib/django/contrib/gis/db/backends/postgis/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base copying build/lib/django/contrib/gis/db/backends/base/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/client.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite copying build/lib/django/contrib/gis/db/backends/spatialite/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/oracle/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle copying build/lib/django/contrib/gis/db/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends copying build/lib/django/contrib/gis/db/backends/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/db/backends/mysql/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql copying build/lib/django/contrib/gis/shortcuts.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis copying build/lib/django/contrib/gis/measure.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis copying build/lib/django/contrib/gis/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps copying build/lib/django/contrib/gis/sitemaps/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps copying build/lib/django/contrib/gis/sitemaps/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps copying build/lib/django/contrib/gis/sitemaps/kml.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps copying build/lib/django/contrib/gis/ptr.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/prepared.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/LICENSE -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/linestring.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/factory.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/point.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/coordseq.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/error.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/geometry.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/io.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/polygon.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/collections.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/threadsafe.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/io.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/predicates.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/errcheck.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/geom.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/coordseq.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/topology.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/misc.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/prototypes/prepared.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes copying build/lib/django/contrib/gis/geos/libgeos.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/geos/mutable_list.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos copying build/lib/django/contrib/gis/feeds.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/testing.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management copying build/lib/django/contrib/staticfiles/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/runserver.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/findstatic.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/management/commands/collectstatic.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands copying build/lib/django/contrib/staticfiles/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/handlers.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/finders.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/storage.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles copying build/lib/django/contrib/staticfiles/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs copying build/lib/django/contrib/admindocs/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES copying build/lib/django/contrib/admindocs/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/view_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/templates/admin_doc/model_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc copying build/lib/django/contrib/admindocs/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs copying build/lib/django/contrib/admindocs/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs copying build/lib/django/contrib/admindocs/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs copying build/lib/django/contrib/admindocs/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs copying build/lib/django/contrib/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib running install_egg_info Copying Django.egg-info to build/bdist.linux-x86_64/wheel/Django-4.2.5-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/Django-4.2.5.dist-info/WHEEL creating '/build/Django-4.2.5/dist/.tmp-m44lub96/Django-4.2.5-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'django/__init__.py' adding 'django/__main__.py' adding 'django/shortcuts.py' adding 'django/apps/__init__.py' adding 'django/apps/config.py' adding 'django/apps/registry.py' adding 'django/conf/__init__.py' adding 'django/conf/__init__.py.orig' adding 'django/conf/global_settings.py' adding 'django/conf/app_template/__init__.py-tpl' adding 'django/conf/app_template/admin.py-tpl' adding 'django/conf/app_template/apps.py-tpl' adding 'django/conf/app_template/models.py-tpl' adding 'django/conf/app_template/tests.py-tpl' adding 'django/conf/app_template/views.py-tpl' adding 'django/conf/app_template/migrations/__init__.py-tpl' adding 'django/conf/locale/__init__.py' adding 'django/conf/locale/af/LC_MESSAGES/django.mo' adding 'django/conf/locale/af/LC_MESSAGES/django.po' adding 'django/conf/locale/ar/__init__.py' adding 'django/conf/locale/ar/formats.py' adding 'django/conf/locale/ar/LC_MESSAGES/django.mo' adding 'django/conf/locale/ar/LC_MESSAGES/django.po' adding 'django/conf/locale/ar_DZ/__init__.py' adding 'django/conf/locale/ar_DZ/formats.py' adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/conf/locale/ast/LC_MESSAGES/django.mo' adding 'django/conf/locale/ast/LC_MESSAGES/django.po' adding 'django/conf/locale/az/__init__.py' adding 'django/conf/locale/az/formats.py' adding 'django/conf/locale/az/LC_MESSAGES/django.mo' adding 'django/conf/locale/az/LC_MESSAGES/django.po' adding 'django/conf/locale/be/LC_MESSAGES/django.mo' adding 'django/conf/locale/be/LC_MESSAGES/django.po' adding 'django/conf/locale/bg/__init__.py' adding 'django/conf/locale/bg/formats.py' adding 'django/conf/locale/bg/LC_MESSAGES/django.mo' adding 'django/conf/locale/bg/LC_MESSAGES/django.po' adding 'django/conf/locale/bn/__init__.py' adding 'django/conf/locale/bn/formats.py' adding 'django/conf/locale/bn/LC_MESSAGES/django.mo' adding 'django/conf/locale/bn/LC_MESSAGES/django.po' adding 'django/conf/locale/br/LC_MESSAGES/django.mo' adding 'django/conf/locale/br/LC_MESSAGES/django.po' adding 'django/conf/locale/bs/__init__.py' adding 'django/conf/locale/bs/formats.py' adding 'django/conf/locale/bs/LC_MESSAGES/django.mo' adding 'django/conf/locale/bs/LC_MESSAGES/django.po' adding 'django/conf/locale/ca/__init__.py' adding 'django/conf/locale/ca/formats.py' adding 'django/conf/locale/ca/LC_MESSAGES/django.mo' adding 'django/conf/locale/ca/LC_MESSAGES/django.po' adding 'django/conf/locale/ckb/__init__.py' adding 'django/conf/locale/ckb/formats.py' adding 'django/conf/locale/ckb/LC_MESSAGES/django.mo' adding 'django/conf/locale/ckb/LC_MESSAGES/django.po' adding 'django/conf/locale/cs/__init__.py' adding 'django/conf/locale/cs/formats.py' adding 'django/conf/locale/cs/LC_MESSAGES/django.mo' adding 'django/conf/locale/cs/LC_MESSAGES/django.po' adding 'django/conf/locale/cy/__init__.py' adding 'django/conf/locale/cy/formats.py' adding 'django/conf/locale/cy/LC_MESSAGES/django.mo' adding 'django/conf/locale/cy/LC_MESSAGES/django.po' adding 'django/conf/locale/da/__init__.py' adding 'django/conf/locale/da/formats.py' adding 'django/conf/locale/da/LC_MESSAGES/django.mo' adding 'django/conf/locale/da/LC_MESSAGES/django.po' adding 'django/conf/locale/de/__init__.py' adding 'django/conf/locale/de/formats.py' adding 'django/conf/locale/de/LC_MESSAGES/django.mo' adding 'django/conf/locale/de/LC_MESSAGES/django.po' adding 'django/conf/locale/de_CH/__init__.py' adding 'django/conf/locale/de_CH/formats.py' adding 'django/conf/locale/dsb/LC_MESSAGES/django.mo' adding 'django/conf/locale/dsb/LC_MESSAGES/django.po' adding 'django/conf/locale/el/__init__.py' adding 'django/conf/locale/el/formats.py' adding 'django/conf/locale/el/LC_MESSAGES/django.mo' adding 'django/conf/locale/el/LC_MESSAGES/django.po' adding 'django/conf/locale/en/__init__.py' adding 'django/conf/locale/en/formats.py' adding 'django/conf/locale/en/LC_MESSAGES/django.mo' adding 'django/conf/locale/en/LC_MESSAGES/django.po' adding 'django/conf/locale/en_AU/__init__.py' adding 'django/conf/locale/en_AU/formats.py' adding 'django/conf/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/conf/locale/en_AU/LC_MESSAGES/django.po' adding 'django/conf/locale/en_GB/__init__.py' adding 'django/conf/locale/en_GB/formats.py' adding 'django/conf/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/conf/locale/en_GB/LC_MESSAGES/django.po' adding 'django/conf/locale/eo/__init__.py' adding 'django/conf/locale/eo/formats.py' adding 'django/conf/locale/eo/LC_MESSAGES/django.mo' adding 'django/conf/locale/eo/LC_MESSAGES/django.po' adding 'django/conf/locale/es/__init__.py' adding 'django/conf/locale/es/formats.py' adding 'django/conf/locale/es/LC_MESSAGES/django.mo' adding 'django/conf/locale/es/LC_MESSAGES/django.po' adding 'django/conf/locale/es_AR/__init__.py' adding 'django/conf/locale/es_AR/formats.py' adding 'django/conf/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/conf/locale/es_AR/LC_MESSAGES/django.po' adding 'django/conf/locale/es_CO/__init__.py' adding 'django/conf/locale/es_CO/formats.py' adding 'django/conf/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/conf/locale/es_CO/LC_MESSAGES/django.po' adding 'django/conf/locale/es_MX/__init__.py' adding 'django/conf/locale/es_MX/formats.py' adding 'django/conf/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/conf/locale/es_MX/LC_MESSAGES/django.po' adding 'django/conf/locale/es_NI/__init__.py' adding 'django/conf/locale/es_NI/formats.py' adding 'django/conf/locale/es_PR/__init__.py' adding 'django/conf/locale/es_PR/formats.py' adding 'django/conf/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/conf/locale/es_VE/LC_MESSAGES/django.po' adding 'django/conf/locale/et/__init__.py' adding 'django/conf/locale/et/formats.py' adding 'django/conf/locale/et/LC_MESSAGES/django.mo' adding 'django/conf/locale/et/LC_MESSAGES/django.po' adding 'django/conf/locale/eu/__init__.py' adding 'django/conf/locale/eu/formats.py' adding 'django/conf/locale/eu/LC_MESSAGES/django.mo' adding 'django/conf/locale/eu/LC_MESSAGES/django.po' adding 'django/conf/locale/fa/__init__.py' adding 'django/conf/locale/fa/formats.py' adding 'django/conf/locale/fa/LC_MESSAGES/django.mo' adding 'django/conf/locale/fa/LC_MESSAGES/django.po' adding 'django/conf/locale/fi/__init__.py' adding 'django/conf/locale/fi/formats.py' adding 'django/conf/locale/fi/LC_MESSAGES/django.mo' adding 'django/conf/locale/fi/LC_MESSAGES/django.po' adding 'django/conf/locale/fr/__init__.py' adding 'django/conf/locale/fr/formats.py' adding 'django/conf/locale/fr/LC_MESSAGES/django.mo' adding 'django/conf/locale/fr/LC_MESSAGES/django.po' adding 'django/conf/locale/fy/__init__.py' adding 'django/conf/locale/fy/formats.py' adding 'django/conf/locale/fy/LC_MESSAGES/django.mo' adding 'django/conf/locale/fy/LC_MESSAGES/django.po' adding 'django/conf/locale/ga/__init__.py' adding 'django/conf/locale/ga/formats.py' adding 'django/conf/locale/ga/LC_MESSAGES/django.mo' adding 'django/conf/locale/ga/LC_MESSAGES/django.po' adding 'django/conf/locale/gd/__init__.py' adding 'django/conf/locale/gd/formats.py' adding 'django/conf/locale/gd/LC_MESSAGES/django.mo' adding 'django/conf/locale/gd/LC_MESSAGES/django.po' adding 'django/conf/locale/gl/__init__.py' adding 'django/conf/locale/gl/formats.py' adding 'django/conf/locale/gl/LC_MESSAGES/django.mo' adding 'django/conf/locale/gl/LC_MESSAGES/django.po' adding 'django/conf/locale/he/__init__.py' adding 'django/conf/locale/he/formats.py' adding 'django/conf/locale/he/LC_MESSAGES/django.mo' adding 'django/conf/locale/he/LC_MESSAGES/django.po' adding 'django/conf/locale/hi/__init__.py' adding 'django/conf/locale/hi/formats.py' adding 'django/conf/locale/hi/LC_MESSAGES/django.mo' adding 'django/conf/locale/hi/LC_MESSAGES/django.po' adding 'django/conf/locale/hr/__init__.py' adding 'django/conf/locale/hr/formats.py' adding 'django/conf/locale/hr/LC_MESSAGES/django.mo' adding 'django/conf/locale/hr/LC_MESSAGES/django.po' adding 'django/conf/locale/hsb/LC_MESSAGES/django.mo' adding 'django/conf/locale/hsb/LC_MESSAGES/django.po' adding 'django/conf/locale/hu/__init__.py' adding 'django/conf/locale/hu/formats.py' adding 'django/conf/locale/hu/LC_MESSAGES/django.mo' adding 'django/conf/locale/hu/LC_MESSAGES/django.po' adding 'django/conf/locale/hy/LC_MESSAGES/django.mo' adding 'django/conf/locale/hy/LC_MESSAGES/django.po' adding 'django/conf/locale/ia/LC_MESSAGES/django.mo' adding 'django/conf/locale/ia/LC_MESSAGES/django.po' adding 'django/conf/locale/id/__init__.py' adding 'django/conf/locale/id/formats.py' adding 'django/conf/locale/id/LC_MESSAGES/django.mo' adding 'django/conf/locale/id/LC_MESSAGES/django.po' adding 'django/conf/locale/ig/__init__.py' adding 'django/conf/locale/ig/formats.py' adding 'django/conf/locale/ig/LC_MESSAGES/django.mo' adding 'django/conf/locale/ig/LC_MESSAGES/django.po' adding 'django/conf/locale/io/LC_MESSAGES/django.mo' adding 'django/conf/locale/io/LC_MESSAGES/django.po' adding 'django/conf/locale/is/__init__.py' adding 'django/conf/locale/is/formats.py' adding 'django/conf/locale/is/LC_MESSAGES/django.mo' adding 'django/conf/locale/is/LC_MESSAGES/django.po' adding 'django/conf/locale/it/__init__.py' adding 'django/conf/locale/it/formats.py' adding 'django/conf/locale/it/LC_MESSAGES/django.mo' adding 'django/conf/locale/it/LC_MESSAGES/django.po' adding 'django/conf/locale/ja/__init__.py' adding 'django/conf/locale/ja/formats.py' adding 'django/conf/locale/ja/LC_MESSAGES/django.mo' adding 'django/conf/locale/ja/LC_MESSAGES/django.po' adding 'django/conf/locale/ka/__init__.py' adding 'django/conf/locale/ka/formats.py' adding 'django/conf/locale/ka/LC_MESSAGES/django.mo' adding 'django/conf/locale/ka/LC_MESSAGES/django.po' adding 'django/conf/locale/kab/LC_MESSAGES/django.mo' adding 'django/conf/locale/kab/LC_MESSAGES/django.po' adding 'django/conf/locale/kk/LC_MESSAGES/django.mo' adding 'django/conf/locale/kk/LC_MESSAGES/django.po' adding 'django/conf/locale/km/__init__.py' adding 'django/conf/locale/km/formats.py' adding 'django/conf/locale/km/LC_MESSAGES/django.mo' adding 'django/conf/locale/km/LC_MESSAGES/django.po' adding 'django/conf/locale/kn/__init__.py' adding 'django/conf/locale/kn/formats.py' adding 'django/conf/locale/kn/LC_MESSAGES/django.mo' adding 'django/conf/locale/kn/LC_MESSAGES/django.po' adding 'django/conf/locale/ko/__init__.py' adding 'django/conf/locale/ko/formats.py' adding 'django/conf/locale/ko/LC_MESSAGES/django.mo' adding 'django/conf/locale/ko/LC_MESSAGES/django.po' adding 'django/conf/locale/ky/__init__.py' adding 'django/conf/locale/ky/formats.py' adding 'django/conf/locale/ky/LC_MESSAGES/django.mo' adding 'django/conf/locale/ky/LC_MESSAGES/django.po' adding 'django/conf/locale/lb/LC_MESSAGES/django.mo' adding 'django/conf/locale/lb/LC_MESSAGES/django.po' adding 'django/conf/locale/lt/__init__.py' adding 'django/conf/locale/lt/formats.py' adding 'django/conf/locale/lt/LC_MESSAGES/django.mo' adding 'django/conf/locale/lt/LC_MESSAGES/django.po' adding 'django/conf/locale/lv/__init__.py' adding 'django/conf/locale/lv/formats.py' adding 'django/conf/locale/lv/LC_MESSAGES/django.mo' adding 'django/conf/locale/lv/LC_MESSAGES/django.po' adding 'django/conf/locale/mk/__init__.py' adding 'django/conf/locale/mk/formats.py' adding 'django/conf/locale/mk/LC_MESSAGES/django.mo' adding 'django/conf/locale/mk/LC_MESSAGES/django.po' adding 'django/conf/locale/ml/__init__.py' adding 'django/conf/locale/ml/formats.py' adding 'django/conf/locale/ml/LC_MESSAGES/django.mo' adding 'django/conf/locale/ml/LC_MESSAGES/django.po' adding 'django/conf/locale/mn/__init__.py' adding 'django/conf/locale/mn/formats.py' adding 'django/conf/locale/mn/LC_MESSAGES/django.mo' adding 'django/conf/locale/mn/LC_MESSAGES/django.po' adding 'django/conf/locale/mr/LC_MESSAGES/django.mo' adding 'django/conf/locale/mr/LC_MESSAGES/django.po' adding 'django/conf/locale/ms/__init__.py' adding 'django/conf/locale/ms/formats.py' adding 'django/conf/locale/ms/LC_MESSAGES/django.mo' adding 'django/conf/locale/ms/LC_MESSAGES/django.po' adding 'django/conf/locale/my/LC_MESSAGES/django.mo' adding 'django/conf/locale/my/LC_MESSAGES/django.po' adding 'django/conf/locale/nb/__init__.py' adding 'django/conf/locale/nb/formats.py' adding 'django/conf/locale/nb/LC_MESSAGES/django.mo' adding 'django/conf/locale/nb/LC_MESSAGES/django.po' adding 'django/conf/locale/ne/LC_MESSAGES/django.mo' adding 'django/conf/locale/ne/LC_MESSAGES/django.po' adding 'django/conf/locale/nl/__init__.py' adding 'django/conf/locale/nl/formats.py' adding 'django/conf/locale/nl/LC_MESSAGES/django.mo' adding 'django/conf/locale/nl/LC_MESSAGES/django.po' adding 'django/conf/locale/nn/__init__.py' adding 'django/conf/locale/nn/formats.py' adding 'django/conf/locale/nn/LC_MESSAGES/django.mo' adding 'django/conf/locale/nn/LC_MESSAGES/django.po' adding 'django/conf/locale/os/LC_MESSAGES/django.mo' adding 'django/conf/locale/os/LC_MESSAGES/django.po' adding 'django/conf/locale/pa/LC_MESSAGES/django.mo' adding 'django/conf/locale/pa/LC_MESSAGES/django.po' adding 'django/conf/locale/pl/__init__.py' adding 'django/conf/locale/pl/formats.py' adding 'django/conf/locale/pl/LC_MESSAGES/django.mo' adding 'django/conf/locale/pl/LC_MESSAGES/django.po' adding 'django/conf/locale/pt/__init__.py' adding 'django/conf/locale/pt/formats.py' adding 'django/conf/locale/pt/LC_MESSAGES/django.mo' adding 'django/conf/locale/pt/LC_MESSAGES/django.po' adding 'django/conf/locale/pt_BR/__init__.py' adding 'django/conf/locale/pt_BR/formats.py' adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/conf/locale/ro/__init__.py' adding 'django/conf/locale/ro/formats.py' adding 'django/conf/locale/ro/LC_MESSAGES/django.mo' adding 'django/conf/locale/ro/LC_MESSAGES/django.po' adding 'django/conf/locale/ru/__init__.py' adding 'django/conf/locale/ru/formats.py' adding 'django/conf/locale/ru/LC_MESSAGES/django.mo' adding 'django/conf/locale/ru/LC_MESSAGES/django.po' adding 'django/conf/locale/sk/__init__.py' adding 'django/conf/locale/sk/formats.py' adding 'django/conf/locale/sk/LC_MESSAGES/django.mo' adding 'django/conf/locale/sk/LC_MESSAGES/django.po' adding 'django/conf/locale/sl/__init__.py' adding 'django/conf/locale/sl/formats.py' adding 'django/conf/locale/sl/LC_MESSAGES/django.mo' adding 'django/conf/locale/sl/LC_MESSAGES/django.po' adding 'django/conf/locale/sq/__init__.py' adding 'django/conf/locale/sq/formats.py' adding 'django/conf/locale/sq/LC_MESSAGES/django.mo' adding 'django/conf/locale/sq/LC_MESSAGES/django.po' adding 'django/conf/locale/sr/__init__.py' adding 'django/conf/locale/sr/formats.py' adding 'django/conf/locale/sr/LC_MESSAGES/django.mo' adding 'django/conf/locale/sr/LC_MESSAGES/django.po' adding 'django/conf/locale/sr_Latn/__init__.py' adding 'django/conf/locale/sr_Latn/formats.py' adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/conf/locale/sv/__init__.py' adding 'django/conf/locale/sv/formats.py' adding 'django/conf/locale/sv/LC_MESSAGES/django.mo' adding 'django/conf/locale/sv/LC_MESSAGES/django.po' adding 'django/conf/locale/sw/LC_MESSAGES/django.mo' adding 'django/conf/locale/sw/LC_MESSAGES/django.po' adding 'django/conf/locale/ta/__init__.py' adding 'django/conf/locale/ta/formats.py' adding 'django/conf/locale/ta/LC_MESSAGES/django.mo' adding 'django/conf/locale/ta/LC_MESSAGES/django.po' adding 'django/conf/locale/te/__init__.py' adding 'django/conf/locale/te/formats.py' adding 'django/conf/locale/te/LC_MESSAGES/django.mo' adding 'django/conf/locale/te/LC_MESSAGES/django.po' adding 'django/conf/locale/tg/__init__.py' adding 'django/conf/locale/tg/formats.py' adding 'django/conf/locale/tg/LC_MESSAGES/django.mo' adding 'django/conf/locale/tg/LC_MESSAGES/django.po' adding 'django/conf/locale/th/__init__.py' adding 'django/conf/locale/th/formats.py' adding 'django/conf/locale/th/LC_MESSAGES/django.mo' adding 'django/conf/locale/th/LC_MESSAGES/django.po' adding 'django/conf/locale/tk/__init__.py' adding 'django/conf/locale/tk/formats.py' adding 'django/conf/locale/tk/LC_MESSAGES/django.mo' adding 'django/conf/locale/tk/LC_MESSAGES/django.po' adding 'django/conf/locale/tr/__init__.py' adding 'django/conf/locale/tr/formats.py' adding 'django/conf/locale/tr/LC_MESSAGES/django.mo' adding 'django/conf/locale/tr/LC_MESSAGES/django.po' adding 'django/conf/locale/tt/LC_MESSAGES/django.mo' adding 'django/conf/locale/tt/LC_MESSAGES/django.po' adding 'django/conf/locale/udm/LC_MESSAGES/django.mo' adding 'django/conf/locale/udm/LC_MESSAGES/django.po' adding 'django/conf/locale/uk/__init__.py' adding 'django/conf/locale/uk/formats.py' adding 'django/conf/locale/uk/LC_MESSAGES/django.mo' adding 'django/conf/locale/uk/LC_MESSAGES/django.po' adding 'django/conf/locale/ur/LC_MESSAGES/django.mo' adding 'django/conf/locale/ur/LC_MESSAGES/django.po' adding 'django/conf/locale/uz/__init__.py' adding 'django/conf/locale/uz/formats.py' adding 'django/conf/locale/uz/LC_MESSAGES/django.mo' adding 'django/conf/locale/uz/LC_MESSAGES/django.po' adding 'django/conf/locale/vi/__init__.py' adding 'django/conf/locale/vi/formats.py' adding 'django/conf/locale/vi/LC_MESSAGES/django.mo' adding 'django/conf/locale/vi/LC_MESSAGES/django.po' adding 'django/conf/locale/zh_Hans/__init__.py' adding 'django/conf/locale/zh_Hans/formats.py' adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/conf/locale/zh_Hant/__init__.py' adding 'django/conf/locale/zh_Hant/formats.py' adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/conf/project_template/manage.py-tpl' adding 'django/conf/project_template/project_name/__init__.py-tpl' adding 'django/conf/project_template/project_name/asgi.py-tpl' adding 'django/conf/project_template/project_name/settings.py-tpl' adding 'django/conf/project_template/project_name/urls.py-tpl' adding 'django/conf/project_template/project_name/wsgi.py-tpl' adding 'django/conf/urls/__init__.py' adding 'django/conf/urls/i18n.py' adding 'django/conf/urls/static.py' adding 'django/contrib/__init__.py' adding 'django/contrib/admin/__init__.py' adding 'django/contrib/admin/actions.py' adding 'django/contrib/admin/apps.py' adding 'django/contrib/admin/checks.py' adding 'django/contrib/admin/decorators.py' adding 'django/contrib/admin/exceptions.py' adding 'django/contrib/admin/filters.py' adding 'django/contrib/admin/forms.py' adding 'django/contrib/admin/helpers.py' adding 'django/contrib/admin/models.py' adding 'django/contrib/admin/options.py' adding 'django/contrib/admin/sites.py' adding 'django/contrib/admin/tests.py' adding 'django/contrib/admin/utils.py' adding 'django/contrib/admin/widgets.py' adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo' adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po' adding 'django/contrib/admin/migrations/0001_initial.py' adding 'django/contrib/admin/migrations/0002_logentry_remove_auto_add.py' adding 'django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py' adding 'django/contrib/admin/migrations/__init__.py' adding 'django/contrib/admin/static/admin/css/autocomplete.css' adding 'django/contrib/admin/static/admin/css/base.css' adding 'django/contrib/admin/static/admin/css/changelists.css' adding 'django/contrib/admin/static/admin/css/dark_mode.css' adding 'django/contrib/admin/static/admin/css/dashboard.css' adding 'django/contrib/admin/static/admin/css/forms.css' adding 'django/contrib/admin/static/admin/css/login.css' adding 'django/contrib/admin/static/admin/css/nav_sidebar.css' adding 'django/contrib/admin/static/admin/css/responsive.css' adding 'django/contrib/admin/static/admin/css/responsive_rtl.css' adding 'django/contrib/admin/static/admin/css/rtl.css' adding 'django/contrib/admin/static/admin/css/widgets.css' adding 'django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md' adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.css' adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.min.css' adding 'django/contrib/admin/static/admin/img/LICENSE' adding 'django/contrib/admin/static/admin/img/README.txt' adding 'django/contrib/admin/static/admin/img/calendar-icons.svg' adding 'django/contrib/admin/static/admin/img/icon-addlink.svg' adding 'django/contrib/admin/static/admin/img/icon-alert.svg' adding 'django/contrib/admin/static/admin/img/icon-calendar.svg' adding 'django/contrib/admin/static/admin/img/icon-changelink.svg' adding 'django/contrib/admin/static/admin/img/icon-clock.svg' adding 'django/contrib/admin/static/admin/img/icon-deletelink.svg' adding 'django/contrib/admin/static/admin/img/icon-no.svg' adding 'django/contrib/admin/static/admin/img/icon-unknown-alt.svg' adding 'django/contrib/admin/static/admin/img/icon-unknown.svg' adding 'django/contrib/admin/static/admin/img/icon-viewlink.svg' adding 'django/contrib/admin/static/admin/img/icon-yes.svg' adding 'django/contrib/admin/static/admin/img/inline-delete.svg' adding 'django/contrib/admin/static/admin/img/search.svg' adding 'django/contrib/admin/static/admin/img/selector-icons.svg' adding 'django/contrib/admin/static/admin/img/sorting-icons.svg' adding 'django/contrib/admin/static/admin/img/tooltag-add.svg' adding 'django/contrib/admin/static/admin/img/tooltag-arrowright.svg' adding 'django/contrib/admin/static/admin/img/gis/move_vertex_off.svg' adding 'django/contrib/admin/static/admin/img/gis/move_vertex_on.svg' adding 'django/contrib/admin/static/admin/js/SelectBox.js' adding 'django/contrib/admin/static/admin/js/SelectFilter2.js' adding 'django/contrib/admin/static/admin/js/actions.js' adding 'django/contrib/admin/static/admin/js/autocomplete.js' adding 'django/contrib/admin/static/admin/js/calendar.js' adding 'django/contrib/admin/static/admin/js/cancel.js' adding 'django/contrib/admin/static/admin/js/change_form.js' adding 'django/contrib/admin/static/admin/js/collapse.js' adding 'django/contrib/admin/static/admin/js/core.js' adding 'django/contrib/admin/static/admin/js/filters.js' adding 'django/contrib/admin/static/admin/js/inlines.js' adding 'django/contrib/admin/static/admin/js/jquery.init.js' adding 'django/contrib/admin/static/admin/js/nav_sidebar.js' adding 'django/contrib/admin/static/admin/js/popup_response.js' adding 'django/contrib/admin/static/admin/js/prepopulate.js' adding 'django/contrib/admin/static/admin/js/prepopulate_init.js' adding 'django/contrib/admin/static/admin/js/theme.js' adding 'django/contrib/admin/static/admin/js/urlify.js' adding 'django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js' adding 'django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js' adding 'django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt' adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.js' adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md' adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js' adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js' adding 'django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt' adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js' adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js' adding 'django/contrib/admin/templates/admin/404.html' adding 'django/contrib/admin/templates/admin/500.html' adding 'django/contrib/admin/templates/admin/actions.html' adding 'django/contrib/admin/templates/admin/app_index.html' adding 'django/contrib/admin/templates/admin/app_list.html' adding 'django/contrib/admin/templates/admin/base.html' adding 'django/contrib/admin/templates/admin/base_site.html' adding 'django/contrib/admin/templates/admin/change_form.html' adding 'django/contrib/admin/templates/admin/change_form_object_tools.html' adding 'django/contrib/admin/templates/admin/change_list.html' adding 'django/contrib/admin/templates/admin/change_list_object_tools.html' adding 'django/contrib/admin/templates/admin/change_list_results.html' adding 'django/contrib/admin/templates/admin/color_theme_toggle.html' adding 'django/contrib/admin/templates/admin/date_hierarchy.html' adding 'django/contrib/admin/templates/admin/delete_confirmation.html' adding 'django/contrib/admin/templates/admin/delete_selected_confirmation.html' adding 'django/contrib/admin/templates/admin/filter.html' adding 'django/contrib/admin/templates/admin/index.html' adding 'django/contrib/admin/templates/admin/invalid_setup.html' adding 'django/contrib/admin/templates/admin/login.html' adding 'django/contrib/admin/templates/admin/nav_sidebar.html' adding 'django/contrib/admin/templates/admin/object_history.html' adding 'django/contrib/admin/templates/admin/pagination.html' adding 'django/contrib/admin/templates/admin/popup_response.html' adding 'django/contrib/admin/templates/admin/prepopulated_fields_js.html' adding 'django/contrib/admin/templates/admin/search_form.html' adding 'django/contrib/admin/templates/admin/submit_line.html' adding 'django/contrib/admin/templates/admin/auth/user/add_form.html' adding 'django/contrib/admin/templates/admin/auth/user/change_password.html' adding 'django/contrib/admin/templates/admin/edit_inline/stacked.html' adding 'django/contrib/admin/templates/admin/edit_inline/tabular.html' adding 'django/contrib/admin/templates/admin/includes/fieldset.html' adding 'django/contrib/admin/templates/admin/includes/object_delete_summary.html' adding 'django/contrib/admin/templates/admin/widgets/clearable_file_input.html' adding 'django/contrib/admin/templates/admin/widgets/date.html' adding 'django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html' adding 'django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html' adding 'django/contrib/admin/templates/admin/widgets/radio.html' adding 'django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html' adding 'django/contrib/admin/templates/admin/widgets/split_datetime.html' adding 'django/contrib/admin/templates/admin/widgets/time.html' adding 'django/contrib/admin/templates/admin/widgets/url.html' adding 'django/contrib/admin/templates/registration/logged_out.html' adding 'django/contrib/admin/templates/registration/password_change_done.html' adding 'django/contrib/admin/templates/registration/password_change_form.html' adding 'django/contrib/admin/templates/registration/password_reset_complete.html' adding 'django/contrib/admin/templates/registration/password_reset_confirm.html' adding 'django/contrib/admin/templates/registration/password_reset_done.html' adding 'django/contrib/admin/templates/registration/password_reset_email.html' adding 'django/contrib/admin/templates/registration/password_reset_form.html' adding 'django/contrib/admin/templatetags/__init__.py' adding 'django/contrib/admin/templatetags/admin_list.py' adding 'django/contrib/admin/templatetags/admin_modify.py' adding 'django/contrib/admin/templatetags/admin_urls.py' adding 'django/contrib/admin/templatetags/base.py' adding 'django/contrib/admin/templatetags/log.py' adding 'django/contrib/admin/views/__init__.py' adding 'django/contrib/admin/views/autocomplete.py' adding 'django/contrib/admin/views/decorators.py' adding 'django/contrib/admin/views/main.py' adding 'django/contrib/admindocs/__init__.py' adding 'django/contrib/admindocs/apps.py' adding 'django/contrib/admindocs/middleware.py' adding 'django/contrib/admindocs/urls.py' adding 'django/contrib/admindocs/utils.py' adding 'django/contrib/admindocs/views.py' adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/admindocs/templates/admin_doc/bookmarklets.html' adding 'django/contrib/admindocs/templates/admin_doc/index.html' adding 'django/contrib/admindocs/templates/admin_doc/missing_docutils.html' adding 'django/contrib/admindocs/templates/admin_doc/model_detail.html' adding 'django/contrib/admindocs/templates/admin_doc/model_index.html' adding 'django/contrib/admindocs/templates/admin_doc/template_detail.html' adding 'django/contrib/admindocs/templates/admin_doc/template_filter_index.html' adding 'django/contrib/admindocs/templates/admin_doc/template_tag_index.html' adding 'django/contrib/admindocs/templates/admin_doc/view_detail.html' adding 'django/contrib/admindocs/templates/admin_doc/view_index.html' adding 'django/contrib/auth/__init__.py' adding 'django/contrib/auth/admin.py' adding 'django/contrib/auth/apps.py' adding 'django/contrib/auth/backends.py' adding 'django/contrib/auth/base_user.py' adding 'django/contrib/auth/checks.py' adding 'django/contrib/auth/common-passwords.txt.gz' adding 'django/contrib/auth/context_processors.py' adding 'django/contrib/auth/decorators.py' adding 'django/contrib/auth/forms.py' adding 'django/contrib/auth/hashers.py' adding 'django/contrib/auth/middleware.py' adding 'django/contrib/auth/mixins.py' adding 'django/contrib/auth/models.py' adding 'django/contrib/auth/password_validation.py' adding 'django/contrib/auth/signals.py' adding 'django/contrib/auth/tokens.py' adding 'django/contrib/auth/urls.py' adding 'django/contrib/auth/validators.py' adding 'django/contrib/auth/views.py' adding 'django/contrib/auth/handlers/__init__.py' adding 'django/contrib/auth/handlers/modwsgi.py' adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/auth/management/__init__.py' adding 'django/contrib/auth/management/commands/__init__.py' adding 'django/contrib/auth/management/commands/changepassword.py' adding 'django/contrib/auth/management/commands/createsuperuser.py' adding 'django/contrib/auth/migrations/0001_initial.py' adding 'django/contrib/auth/migrations/0002_alter_permission_name_max_length.py' adding 'django/contrib/auth/migrations/0003_alter_user_email_max_length.py' adding 'django/contrib/auth/migrations/0004_alter_user_username_opts.py' adding 'django/contrib/auth/migrations/0005_alter_user_last_login_null.py' adding 'django/contrib/auth/migrations/0006_require_contenttypes_0002.py' adding 'django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py' adding 'django/contrib/auth/migrations/0008_alter_user_username_max_length.py' adding 'django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py' adding 'django/contrib/auth/migrations/0010_alter_group_name_max_length.py' adding 'django/contrib/auth/migrations/0011_update_proxy_permissions.py' adding 'django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py' adding 'django/contrib/auth/migrations/__init__.py' adding 'django/contrib/auth/templates/auth/widgets/read_only_password_hash.html' adding 'django/contrib/auth/templates/registration/password_reset_subject.txt' adding 'django/contrib/contenttypes/__init__.py' adding 'django/contrib/contenttypes/admin.py' adding 'django/contrib/contenttypes/apps.py' adding 'django/contrib/contenttypes/checks.py' adding 'django/contrib/contenttypes/fields.py' adding 'django/contrib/contenttypes/forms.py' adding 'django/contrib/contenttypes/models.py' adding 'django/contrib/contenttypes/views.py' adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/contenttypes/management/__init__.py' adding 'django/contrib/contenttypes/management/commands/__init__.py' adding 'django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py' adding 'django/contrib/contenttypes/migrations/0001_initial.py' adding 'django/contrib/contenttypes/migrations/0002_remove_content_type_name.py' adding 'django/contrib/contenttypes/migrations/__init__.py' adding 'django/contrib/flatpages/__init__.py' adding 'django/contrib/flatpages/admin.py' adding 'django/contrib/flatpages/apps.py' adding 'django/contrib/flatpages/forms.py' adding 'django/contrib/flatpages/middleware.py' adding 'django/contrib/flatpages/models.py' adding 'django/contrib/flatpages/sitemaps.py' adding 'django/contrib/flatpages/urls.py' adding 'django/contrib/flatpages/views.py' adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/flatpages/migrations/0001_initial.py' adding 'django/contrib/flatpages/migrations/__init__.py' adding 'django/contrib/flatpages/templatetags/__init__.py' adding 'django/contrib/flatpages/templatetags/flatpages.py' adding 'django/contrib/gis/__init__.py' adding 'django/contrib/gis/apps.py' adding 'django/contrib/gis/feeds.py' adding 'django/contrib/gis/geometry.py' adding 'django/contrib/gis/measure.py' adding 'django/contrib/gis/ptr.py' adding 'django/contrib/gis/shortcuts.py' adding 'django/contrib/gis/views.py' adding 'django/contrib/gis/admin/__init__.py' adding 'django/contrib/gis/admin/options.py' adding 'django/contrib/gis/admin/widgets.py' adding 'django/contrib/gis/db/__init__.py' adding 'django/contrib/gis/db/backends/__init__.py' adding 'django/contrib/gis/db/backends/utils.py' adding 'django/contrib/gis/db/backends/base/__init__.py' adding 'django/contrib/gis/db/backends/base/adapter.py' adding 'django/contrib/gis/db/backends/base/features.py' adding 'django/contrib/gis/db/backends/base/models.py' adding 'django/contrib/gis/db/backends/base/operations.py' adding 'django/contrib/gis/db/backends/mysql/__init__.py' adding 'django/contrib/gis/db/backends/mysql/base.py' adding 'django/contrib/gis/db/backends/mysql/features.py' adding 'django/contrib/gis/db/backends/mysql/introspection.py' adding 'django/contrib/gis/db/backends/mysql/operations.py' adding 'django/contrib/gis/db/backends/mysql/schema.py' adding 'django/contrib/gis/db/backends/oracle/__init__.py' adding 'django/contrib/gis/db/backends/oracle/adapter.py' adding 'django/contrib/gis/db/backends/oracle/base.py' adding 'django/contrib/gis/db/backends/oracle/features.py' adding 'django/contrib/gis/db/backends/oracle/introspection.py' adding 'django/contrib/gis/db/backends/oracle/models.py' adding 'django/contrib/gis/db/backends/oracle/operations.py' adding 'django/contrib/gis/db/backends/oracle/schema.py' adding 'django/contrib/gis/db/backends/postgis/__init__.py' adding 'django/contrib/gis/db/backends/postgis/adapter.py' adding 'django/contrib/gis/db/backends/postgis/base.py' adding 'django/contrib/gis/db/backends/postgis/const.py' adding 'django/contrib/gis/db/backends/postgis/features.py' adding 'django/contrib/gis/db/backends/postgis/introspection.py' adding 'django/contrib/gis/db/backends/postgis/models.py' adding 'django/contrib/gis/db/backends/postgis/operations.py' adding 'django/contrib/gis/db/backends/postgis/pgraster.py' adding 'django/contrib/gis/db/backends/postgis/schema.py' adding 'django/contrib/gis/db/backends/spatialite/__init__.py' adding 'django/contrib/gis/db/backends/spatialite/adapter.py' adding 'django/contrib/gis/db/backends/spatialite/base.py' adding 'django/contrib/gis/db/backends/spatialite/client.py' adding 'django/contrib/gis/db/backends/spatialite/features.py' adding 'django/contrib/gis/db/backends/spatialite/introspection.py' adding 'django/contrib/gis/db/backends/spatialite/models.py' adding 'django/contrib/gis/db/backends/spatialite/operations.py' adding 'django/contrib/gis/db/backends/spatialite/schema.py' adding 'django/contrib/gis/db/models/__init__.py' adding 'django/contrib/gis/db/models/aggregates.py' adding 'django/contrib/gis/db/models/fields.py' adding 'django/contrib/gis/db/models/functions.py' adding 'django/contrib/gis/db/models/lookups.py' adding 'django/contrib/gis/db/models/proxy.py' adding 'django/contrib/gis/db/models/sql/__init__.py' adding 'django/contrib/gis/db/models/sql/conversion.py' adding 'django/contrib/gis/forms/__init__.py' adding 'django/contrib/gis/forms/fields.py' adding 'django/contrib/gis/forms/widgets.py' adding 'django/contrib/gis/gdal/LICENSE' adding 'django/contrib/gis/gdal/__init__.py' adding 'django/contrib/gis/gdal/base.py' adding 'django/contrib/gis/gdal/datasource.py' adding 'django/contrib/gis/gdal/driver.py' adding 'django/contrib/gis/gdal/envelope.py' adding 'django/contrib/gis/gdal/error.py' adding 'django/contrib/gis/gdal/feature.py' adding 'django/contrib/gis/gdal/field.py' adding 'django/contrib/gis/gdal/geometries.py' adding 'django/contrib/gis/gdal/geomtype.py' adding 'django/contrib/gis/gdal/layer.py' adding 'django/contrib/gis/gdal/libgdal.py' adding 'django/contrib/gis/gdal/srs.py' adding 'django/contrib/gis/gdal/prototypes/__init__.py' adding 'django/contrib/gis/gdal/prototypes/ds.py' adding 'django/contrib/gis/gdal/prototypes/errcheck.py' adding 'django/contrib/gis/gdal/prototypes/generation.py' adding 'django/contrib/gis/gdal/prototypes/geom.py' adding 'django/contrib/gis/gdal/prototypes/raster.py' adding 'django/contrib/gis/gdal/prototypes/srs.py' adding 'django/contrib/gis/gdal/raster/__init__.py' adding 'django/contrib/gis/gdal/raster/band.py' adding 'django/contrib/gis/gdal/raster/base.py' adding 'django/contrib/gis/gdal/raster/const.py' adding 'django/contrib/gis/gdal/raster/source.py' adding 'django/contrib/gis/geoip2/__init__.py' adding 'django/contrib/gis/geoip2/base.py' adding 'django/contrib/gis/geoip2/resources.py' adding 'django/contrib/gis/geos/LICENSE' adding 'django/contrib/gis/geos/__init__.py' adding 'django/contrib/gis/geos/base.py' adding 'django/contrib/gis/geos/collections.py' adding 'django/contrib/gis/geos/coordseq.py' adding 'django/contrib/gis/geos/error.py' adding 'django/contrib/gis/geos/factory.py' adding 'django/contrib/gis/geos/geometry.py' adding 'django/contrib/gis/geos/io.py' adding 'django/contrib/gis/geos/libgeos.py' adding 'django/contrib/gis/geos/linestring.py' adding 'django/contrib/gis/geos/mutable_list.py' adding 'django/contrib/gis/geos/point.py' adding 'django/contrib/gis/geos/polygon.py' adding 'django/contrib/gis/geos/prepared.py' adding 'django/contrib/gis/geos/prototypes/__init__.py' adding 'django/contrib/gis/geos/prototypes/coordseq.py' adding 'django/contrib/gis/geos/prototypes/errcheck.py' adding 'django/contrib/gis/geos/prototypes/geom.py' adding 'django/contrib/gis/geos/prototypes/io.py' adding 'django/contrib/gis/geos/prototypes/misc.py' adding 'django/contrib/gis/geos/prototypes/predicates.py' adding 'django/contrib/gis/geos/prototypes/prepared.py' adding 'django/contrib/gis/geos/prototypes/threadsafe.py' adding 'django/contrib/gis/geos/prototypes/topology.py' adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/gis/management/__init__.py' adding 'django/contrib/gis/management/commands/__init__.py' adding 'django/contrib/gis/management/commands/inspectdb.py' adding 'django/contrib/gis/management/commands/ogrinspect.py' adding 'django/contrib/gis/serializers/__init__.py' adding 'django/contrib/gis/serializers/geojson.py' adding 'django/contrib/gis/sitemaps/__init__.py' adding 'django/contrib/gis/sitemaps/kml.py' adding 'django/contrib/gis/sitemaps/views.py' adding 'django/contrib/gis/static/gis/css/ol3.css' adding 'django/contrib/gis/static/gis/img/draw_line_off.svg' adding 'django/contrib/gis/static/gis/img/draw_line_on.svg' adding 'django/contrib/gis/static/gis/img/draw_point_off.svg' adding 'django/contrib/gis/static/gis/img/draw_point_on.svg' adding 'django/contrib/gis/static/gis/img/draw_polygon_off.svg' adding 'django/contrib/gis/static/gis/img/draw_polygon_on.svg' adding 'django/contrib/gis/static/gis/js/OLMapWidget.js' adding 'django/contrib/gis/templates/gis/openlayers-osm.html' adding 'django/contrib/gis/templates/gis/openlayers.html' adding 'django/contrib/gis/templates/gis/admin/openlayers.html' adding 'django/contrib/gis/templates/gis/admin/openlayers.js' adding 'django/contrib/gis/templates/gis/admin/osm.html' adding 'django/contrib/gis/templates/gis/admin/osm.js' adding 'django/contrib/gis/templates/gis/kml/base.kml' adding 'django/contrib/gis/templates/gis/kml/placemarks.kml' adding 'django/contrib/gis/utils/__init__.py' adding 'django/contrib/gis/utils/layermapping.py' adding 'django/contrib/gis/utils/ogrinfo.py' adding 'django/contrib/gis/utils/ogrinspect.py' adding 'django/contrib/gis/utils/srs.py' adding 'django/contrib/humanize/__init__.py' adding 'django/contrib/humanize/apps.py' adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/humanize/templatetags/__init__.py' adding 'django/contrib/humanize/templatetags/humanize.py' adding 'django/contrib/messages/__init__.py' adding 'django/contrib/messages/api.py' adding 'django/contrib/messages/apps.py' adding 'django/contrib/messages/constants.py' adding 'django/contrib/messages/context_processors.py' adding 'django/contrib/messages/middleware.py' adding 'django/contrib/messages/utils.py' adding 'django/contrib/messages/views.py' adding 'django/contrib/messages/storage/__init__.py' adding 'django/contrib/messages/storage/base.py' adding 'django/contrib/messages/storage/cookie.py' adding 'django/contrib/messages/storage/fallback.py' adding 'django/contrib/messages/storage/session.py' adding 'django/contrib/postgres/__init__.py' adding 'django/contrib/postgres/apps.py' adding 'django/contrib/postgres/constraints.py' adding 'django/contrib/postgres/expressions.py' adding 'django/contrib/postgres/functions.py' adding 'django/contrib/postgres/indexes.py' adding 'django/contrib/postgres/lookups.py' adding 'django/contrib/postgres/operations.py' adding 'django/contrib/postgres/search.py' adding 'django/contrib/postgres/serializers.py' adding 'django/contrib/postgres/signals.py' adding 'django/contrib/postgres/utils.py' adding 'django/contrib/postgres/validators.py' adding 'django/contrib/postgres/aggregates/__init__.py' adding 'django/contrib/postgres/aggregates/general.py' adding 'django/contrib/postgres/aggregates/mixins.py' adding 'django/contrib/postgres/aggregates/statistics.py' adding 'django/contrib/postgres/fields/__init__.py' adding 'django/contrib/postgres/fields/array.py' adding 'django/contrib/postgres/fields/citext.py' adding 'django/contrib/postgres/fields/hstore.py' adding 'django/contrib/postgres/fields/jsonb.py' adding 'django/contrib/postgres/fields/ranges.py' adding 'django/contrib/postgres/fields/utils.py' adding 'django/contrib/postgres/forms/__init__.py' adding 'django/contrib/postgres/forms/array.py' adding 'django/contrib/postgres/forms/hstore.py' adding 'django/contrib/postgres/forms/ranges.py' adding 'django/contrib/postgres/jinja2/postgres/widgets/split_array.html' adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/postgres/templates/postgres/widgets/split_array.html' adding 'django/contrib/redirects/__init__.py' adding 'django/contrib/redirects/admin.py' adding 'django/contrib/redirects/apps.py' adding 'django/contrib/redirects/middleware.py' adding 'django/contrib/redirects/models.py' adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/redirects/migrations/0001_initial.py' adding 'django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py' adding 'django/contrib/redirects/migrations/__init__.py' adding 'django/contrib/sessions/__init__.py' adding 'django/contrib/sessions/apps.py' adding 'django/contrib/sessions/base_session.py' adding 'django/contrib/sessions/exceptions.py' adding 'django/contrib/sessions/middleware.py' adding 'django/contrib/sessions/models.py' adding 'django/contrib/sessions/serializers.py' adding 'django/contrib/sessions/backends/__init__.py' adding 'django/contrib/sessions/backends/base.py' adding 'django/contrib/sessions/backends/cache.py' adding 'django/contrib/sessions/backends/cached_db.py' adding 'django/contrib/sessions/backends/db.py' adding 'django/contrib/sessions/backends/file.py' adding 'django/contrib/sessions/backends/signed_cookies.py' adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/sessions/management/__init__.py' adding 'django/contrib/sessions/management/commands/__init__.py' adding 'django/contrib/sessions/management/commands/clearsessions.py' adding 'django/contrib/sessions/migrations/0001_initial.py' adding 'django/contrib/sessions/migrations/__init__.py' adding 'django/contrib/sitemaps/__init__.py' adding 'django/contrib/sitemaps/apps.py' adding 'django/contrib/sitemaps/views.py' adding 'django/contrib/sitemaps/management/__init__.py' adding 'django/contrib/sitemaps/management/commands/__init__.py' adding 'django/contrib/sitemaps/management/commands/ping_google.py' adding 'django/contrib/sitemaps/templates/sitemap.xml' adding 'django/contrib/sitemaps/templates/sitemap_index.xml' adding 'django/contrib/sites/__init__.py' adding 'django/contrib/sites/admin.py' adding 'django/contrib/sites/apps.py' adding 'django/contrib/sites/checks.py' adding 'django/contrib/sites/management.py' adding 'django/contrib/sites/managers.py' adding 'django/contrib/sites/middleware.py' adding 'django/contrib/sites/models.py' adding 'django/contrib/sites/requests.py' adding 'django/contrib/sites/shortcuts.py' adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django/contrib/sites/migrations/0001_initial.py' adding 'django/contrib/sites/migrations/0002_alter_domain_unique.py' adding 'django/contrib/sites/migrations/__init__.py' adding 'django/contrib/staticfiles/__init__.py' adding 'django/contrib/staticfiles/apps.py' adding 'django/contrib/staticfiles/checks.py' adding 'django/contrib/staticfiles/finders.py' adding 'django/contrib/staticfiles/handlers.py' adding 'django/contrib/staticfiles/storage.py' adding 'django/contrib/staticfiles/testing.py' adding 'django/contrib/staticfiles/urls.py' adding 'django/contrib/staticfiles/utils.py' adding 'django/contrib/staticfiles/views.py' adding 'django/contrib/staticfiles/management/__init__.py' adding 'django/contrib/staticfiles/management/commands/__init__.py' adding 'django/contrib/staticfiles/management/commands/collectstatic.py' adding 'django/contrib/staticfiles/management/commands/findstatic.py' adding 'django/contrib/staticfiles/management/commands/runserver.py' adding 'django/contrib/syndication/__init__.py' adding 'django/contrib/syndication/apps.py' adding 'django/contrib/syndication/views.py' adding 'django/core/__init__.py' adding 'django/core/asgi.py' adding 'django/core/exceptions.py' adding 'django/core/paginator.py' adding 'django/core/signals.py' adding 'django/core/signing.py' adding 'django/core/validators.py' adding 'django/core/wsgi.py' adding 'django/core/cache/__init__.py' adding 'django/core/cache/utils.py' adding 'django/core/cache/backends/__init__.py' adding 'django/core/cache/backends/base.py' adding 'django/core/cache/backends/db.py' adding 'django/core/cache/backends/dummy.py' adding 'django/core/cache/backends/filebased.py' adding 'django/core/cache/backends/locmem.py' adding 'django/core/cache/backends/memcached.py' adding 'django/core/cache/backends/redis.py' adding 'django/core/checks/__init__.py' adding 'django/core/checks/async_checks.py' adding 'django/core/checks/caches.py' adding 'django/core/checks/database.py' adding 'django/core/checks/files.py' adding 'django/core/checks/messages.py' adding 'django/core/checks/model_checks.py' adding 'django/core/checks/registry.py' adding 'django/core/checks/templates.py' adding 'django/core/checks/translation.py' adding 'django/core/checks/urls.py' adding 'django/core/checks/compatibility/__init__.py' adding 'django/core/checks/compatibility/django_4_0.py' adding 'django/core/checks/security/__init__.py' adding 'django/core/checks/security/base.py' adding 'django/core/checks/security/csrf.py' adding 'django/core/checks/security/sessions.py' adding 'django/core/files/__init__.py' adding 'django/core/files/base.py' adding 'django/core/files/images.py' adding 'django/core/files/locks.py' adding 'django/core/files/move.py' adding 'django/core/files/temp.py' adding 'django/core/files/uploadedfile.py' adding 'django/core/files/uploadhandler.py' adding 'django/core/files/utils.py' adding 'django/core/files/storage/__init__.py' adding 'django/core/files/storage/base.py' adding 'django/core/files/storage/filesystem.py' adding 'django/core/files/storage/handler.py' adding 'django/core/files/storage/memory.py' adding 'django/core/files/storage/mixins.py' adding 'django/core/handlers/__init__.py' adding 'django/core/handlers/asgi.py' adding 'django/core/handlers/base.py' adding 'django/core/handlers/exception.py' adding 'django/core/handlers/wsgi.py' adding 'django/core/mail/__init__.py' adding 'django/core/mail/message.py' adding 'django/core/mail/utils.py' adding 'django/core/mail/backends/__init__.py' adding 'django/core/mail/backends/base.py' adding 'django/core/mail/backends/console.py' adding 'django/core/mail/backends/dummy.py' adding 'django/core/mail/backends/filebased.py' adding 'django/core/mail/backends/locmem.py' adding 'django/core/mail/backends/smtp.py' adding 'django/core/management/__init__.py' adding 'django/core/management/base.py' adding 'django/core/management/color.py' adding 'django/core/management/sql.py' adding 'django/core/management/templates.py' adding 'django/core/management/utils.py' adding 'django/core/management/commands/__init__.py' adding 'django/core/management/commands/check.py' adding 'django/core/management/commands/compilemessages.py' adding 'django/core/management/commands/createcachetable.py' adding 'django/core/management/commands/dbshell.py' adding 'django/core/management/commands/diffsettings.py' adding 'django/core/management/commands/dumpdata.py' adding 'django/core/management/commands/flush.py' adding 'django/core/management/commands/inspectdb.py' adding 'django/core/management/commands/loaddata.py' adding 'django/core/management/commands/makemessages.py' adding 'django/core/management/commands/makemigrations.py' adding 'django/core/management/commands/migrate.py' adding 'django/core/management/commands/optimizemigration.py' adding 'django/core/management/commands/runserver.py' adding 'django/core/management/commands/sendtestemail.py' adding 'django/core/management/commands/shell.py' adding 'django/core/management/commands/showmigrations.py' adding 'django/core/management/commands/sqlflush.py' adding 'django/core/management/commands/sqlmigrate.py' adding 'django/core/management/commands/sqlsequencereset.py' adding 'django/core/management/commands/squashmigrations.py' adding 'django/core/management/commands/startapp.py' adding 'django/core/management/commands/startproject.py' adding 'django/core/management/commands/test.py' adding 'django/core/management/commands/testserver.py' adding 'django/core/serializers/__init__.py' adding 'django/core/serializers/base.py' adding 'django/core/serializers/json.py' adding 'django/core/serializers/jsonl.py' adding 'django/core/serializers/python.py' adding 'django/core/serializers/pyyaml.py' adding 'django/core/serializers/xml_serializer.py' adding 'django/core/servers/__init__.py' adding 'django/core/servers/basehttp.py' adding 'django/db/__init__.py' adding 'django/db/transaction.py' adding 'django/db/utils.py' adding 'django/db/backends/__init__.py' adding 'django/db/backends/ddl_references.py' adding 'django/db/backends/signals.py' adding 'django/db/backends/utils.py' adding 'django/db/backends/base/__init__.py' adding 'django/db/backends/base/base.py' adding 'django/db/backends/base/client.py' adding 'django/db/backends/base/creation.py' adding 'django/db/backends/base/features.py' adding 'django/db/backends/base/introspection.py' adding 'django/db/backends/base/operations.py' adding 'django/db/backends/base/schema.py' adding 'django/db/backends/base/validation.py' adding 'django/db/backends/dummy/__init__.py' adding 'django/db/backends/dummy/base.py' adding 'django/db/backends/dummy/features.py' adding 'django/db/backends/mysql/__init__.py' adding 'django/db/backends/mysql/base.py' adding 'django/db/backends/mysql/client.py' adding 'django/db/backends/mysql/compiler.py' adding 'django/db/backends/mysql/creation.py' adding 'django/db/backends/mysql/features.py' adding 'django/db/backends/mysql/introspection.py' adding 'django/db/backends/mysql/operations.py' adding 'django/db/backends/mysql/schema.py' adding 'django/db/backends/mysql/validation.py' adding 'django/db/backends/oracle/__init__.py' adding 'django/db/backends/oracle/base.py' adding 'django/db/backends/oracle/client.py' adding 'django/db/backends/oracle/creation.py' adding 'django/db/backends/oracle/features.py' adding 'django/db/backends/oracle/functions.py' adding 'django/db/backends/oracle/introspection.py' adding 'django/db/backends/oracle/operations.py' adding 'django/db/backends/oracle/schema.py' adding 'django/db/backends/oracle/utils.py' adding 'django/db/backends/oracle/validation.py' adding 'django/db/backends/postgresql/__init__.py' adding 'django/db/backends/postgresql/base.py' adding 'django/db/backends/postgresql/client.py' adding 'django/db/backends/postgresql/creation.py' adding 'django/db/backends/postgresql/features.py' adding 'django/db/backends/postgresql/introspection.py' adding 'django/db/backends/postgresql/operations.py' adding 'django/db/backends/postgresql/psycopg_any.py' adding 'django/db/backends/postgresql/schema.py' adding 'django/db/backends/sqlite3/__init__.py' adding 'django/db/backends/sqlite3/_functions.py' adding 'django/db/backends/sqlite3/base.py' adding 'django/db/backends/sqlite3/client.py' adding 'django/db/backends/sqlite3/creation.py' adding 'django/db/backends/sqlite3/features.py' adding 'django/db/backends/sqlite3/introspection.py' adding 'django/db/backends/sqlite3/operations.py' adding 'django/db/backends/sqlite3/schema.py' adding 'django/db/migrations/__init__.py' adding 'django/db/migrations/autodetector.py' adding 'django/db/migrations/exceptions.py' adding 'django/db/migrations/executor.py' adding 'django/db/migrations/graph.py' adding 'django/db/migrations/loader.py' adding 'django/db/migrations/migration.py' adding 'django/db/migrations/optimizer.py' adding 'django/db/migrations/questioner.py' adding 'django/db/migrations/recorder.py' adding 'django/db/migrations/serializer.py' adding 'django/db/migrations/state.py' adding 'django/db/migrations/utils.py' adding 'django/db/migrations/writer.py' adding 'django/db/migrations/operations/__init__.py' adding 'django/db/migrations/operations/base.py' adding 'django/db/migrations/operations/fields.py' adding 'django/db/migrations/operations/models.py' adding 'django/db/migrations/operations/special.py' adding 'django/db/models/__init__.py' adding 'django/db/models/aggregates.py' adding 'django/db/models/base.py' adding 'django/db/models/constants.py' adding 'django/db/models/constraints.py' adding 'django/db/models/deletion.py' adding 'django/db/models/enums.py' adding 'django/db/models/expressions.py' adding 'django/db/models/indexes.py' adding 'django/db/models/lookups.py' adding 'django/db/models/manager.py' adding 'django/db/models/options.py' adding 'django/db/models/query.py' adding 'django/db/models/query_utils.py' adding 'django/db/models/signals.py' adding 'django/db/models/utils.py' adding 'django/db/models/fields/__init__.py' adding 'django/db/models/fields/files.py' adding 'django/db/models/fields/json.py' adding 'django/db/models/fields/mixins.py' adding 'django/db/models/fields/proxy.py' adding 'django/db/models/fields/related.py' adding 'django/db/models/fields/related_descriptors.py' adding 'django/db/models/fields/related_lookups.py' adding 'django/db/models/fields/reverse_related.py' adding 'django/db/models/functions/__init__.py' adding 'django/db/models/functions/comparison.py' adding 'django/db/models/functions/datetime.py' adding 'django/db/models/functions/math.py' adding 'django/db/models/functions/mixins.py' adding 'django/db/models/functions/text.py' adding 'django/db/models/functions/window.py' adding 'django/db/models/sql/__init__.py' adding 'django/db/models/sql/compiler.py' adding 'django/db/models/sql/constants.py' adding 'django/db/models/sql/datastructures.py' adding 'django/db/models/sql/query.py' adding 'django/db/models/sql/subqueries.py' adding 'django/db/models/sql/where.py' adding 'django/dispatch/__init__.py' adding 'django/dispatch/dispatcher.py' adding 'django/dispatch/license.txt' adding 'django/forms/__init__.py' adding 'django/forms/boundfield.py' adding 'django/forms/fields.py' adding 'django/forms/forms.py' adding 'django/forms/formsets.py' adding 'django/forms/models.py' adding 'django/forms/renderers.py' adding 'django/forms/utils.py' adding 'django/forms/widgets.py' adding 'django/forms/jinja2/django/forms/attrs.html' adding 'django/forms/jinja2/django/forms/default.html' adding 'django/forms/jinja2/django/forms/div.html' adding 'django/forms/jinja2/django/forms/label.html' adding 'django/forms/jinja2/django/forms/p.html' adding 'django/forms/jinja2/django/forms/table.html' adding 'django/forms/jinja2/django/forms/ul.html' adding 'django/forms/jinja2/django/forms/errors/dict/default.html' adding 'django/forms/jinja2/django/forms/errors/dict/text.txt' adding 'django/forms/jinja2/django/forms/errors/dict/ul.html' adding 'django/forms/jinja2/django/forms/errors/list/default.html' adding 'django/forms/jinja2/django/forms/errors/list/text.txt' adding 'django/forms/jinja2/django/forms/errors/list/ul.html' adding 'django/forms/jinja2/django/forms/formsets/default.html' adding 'django/forms/jinja2/django/forms/formsets/div.html' adding 'django/forms/jinja2/django/forms/formsets/p.html' adding 'django/forms/jinja2/django/forms/formsets/table.html' adding 'django/forms/jinja2/django/forms/formsets/ul.html' adding 'django/forms/jinja2/django/forms/widgets/attrs.html' adding 'django/forms/jinja2/django/forms/widgets/checkbox.html' adding 'django/forms/jinja2/django/forms/widgets/checkbox_option.html' adding 'django/forms/jinja2/django/forms/widgets/checkbox_select.html' adding 'django/forms/jinja2/django/forms/widgets/clearable_file_input.html' adding 'django/forms/jinja2/django/forms/widgets/date.html' adding 'django/forms/jinja2/django/forms/widgets/datetime.html' adding 'django/forms/jinja2/django/forms/widgets/email.html' adding 'django/forms/jinja2/django/forms/widgets/file.html' adding 'django/forms/jinja2/django/forms/widgets/hidden.html' adding 'django/forms/jinja2/django/forms/widgets/input.html' adding 'django/forms/jinja2/django/forms/widgets/input_option.html' adding 'django/forms/jinja2/django/forms/widgets/multiple_hidden.html' adding 'django/forms/jinja2/django/forms/widgets/multiple_input.html' adding 'django/forms/jinja2/django/forms/widgets/multiwidget.html' adding 'django/forms/jinja2/django/forms/widgets/number.html' adding 'django/forms/jinja2/django/forms/widgets/password.html' adding 'django/forms/jinja2/django/forms/widgets/radio.html' adding 'django/forms/jinja2/django/forms/widgets/radio_option.html' adding 'django/forms/jinja2/django/forms/widgets/select.html' adding 'django/forms/jinja2/django/forms/widgets/select_date.html' adding 'django/forms/jinja2/django/forms/widgets/select_option.html' adding 'django/forms/jinja2/django/forms/widgets/splitdatetime.html' adding 'django/forms/jinja2/django/forms/widgets/splithiddendatetime.html' adding 'django/forms/jinja2/django/forms/widgets/text.html' adding 'django/forms/jinja2/django/forms/widgets/textarea.html' adding 'django/forms/jinja2/django/forms/widgets/time.html' adding 'django/forms/jinja2/django/forms/widgets/url.html' adding 'django/forms/templates/django/forms/attrs.html' adding 'django/forms/templates/django/forms/default.html' adding 'django/forms/templates/django/forms/div.html' adding 'django/forms/templates/django/forms/label.html' adding 'django/forms/templates/django/forms/p.html' adding 'django/forms/templates/django/forms/table.html' adding 'django/forms/templates/django/forms/ul.html' adding 'django/forms/templates/django/forms/errors/dict/default.html' adding 'django/forms/templates/django/forms/errors/dict/text.txt' adding 'django/forms/templates/django/forms/errors/dict/ul.html' adding 'django/forms/templates/django/forms/errors/list/default.html' adding 'django/forms/templates/django/forms/errors/list/text.txt' adding 'django/forms/templates/django/forms/errors/list/ul.html' adding 'django/forms/templates/django/forms/formsets/default.html' adding 'django/forms/templates/django/forms/formsets/div.html' adding 'django/forms/templates/django/forms/formsets/p.html' adding 'django/forms/templates/django/forms/formsets/table.html' adding 'django/forms/templates/django/forms/formsets/ul.html' adding 'django/forms/templates/django/forms/widgets/attrs.html' adding 'django/forms/templates/django/forms/widgets/checkbox.html' adding 'django/forms/templates/django/forms/widgets/checkbox_option.html' adding 'django/forms/templates/django/forms/widgets/checkbox_select.html' adding 'django/forms/templates/django/forms/widgets/clearable_file_input.html' adding 'django/forms/templates/django/forms/widgets/date.html' adding 'django/forms/templates/django/forms/widgets/datetime.html' adding 'django/forms/templates/django/forms/widgets/email.html' adding 'django/forms/templates/django/forms/widgets/file.html' adding 'django/forms/templates/django/forms/widgets/hidden.html' adding 'django/forms/templates/django/forms/widgets/input.html' adding 'django/forms/templates/django/forms/widgets/input_option.html' adding 'django/forms/templates/django/forms/widgets/multiple_hidden.html' adding 'django/forms/templates/django/forms/widgets/multiple_input.html' adding 'django/forms/templates/django/forms/widgets/multiwidget.html' adding 'django/forms/templates/django/forms/widgets/number.html' adding 'django/forms/templates/django/forms/widgets/password.html' adding 'django/forms/templates/django/forms/widgets/radio.html' adding 'django/forms/templates/django/forms/widgets/radio_option.html' adding 'django/forms/templates/django/forms/widgets/select.html' adding 'django/forms/templates/django/forms/widgets/select_date.html' adding 'django/forms/templates/django/forms/widgets/select_option.html' adding 'django/forms/templates/django/forms/widgets/splitdatetime.html' adding 'django/forms/templates/django/forms/widgets/splithiddendatetime.html' adding 'django/forms/templates/django/forms/widgets/text.html' adding 'django/forms/templates/django/forms/widgets/textarea.html' adding 'django/forms/templates/django/forms/widgets/time.html' adding 'django/forms/templates/django/forms/widgets/url.html' adding 'django/http/__init__.py' adding 'django/http/cookie.py' adding 'django/http/multipartparser.py' adding 'django/http/request.py' adding 'django/http/response.py' adding 'django/middleware/__init__.py' adding 'django/middleware/cache.py' adding 'django/middleware/clickjacking.py' adding 'django/middleware/common.py' adding 'django/middleware/csrf.py' adding 'django/middleware/gzip.py' adding 'django/middleware/http.py' adding 'django/middleware/locale.py' adding 'django/middleware/security.py' adding 'django/template/__init__.py' adding 'django/template/autoreload.py' adding 'django/template/base.py' adding 'django/template/context.py' adding 'django/template/context_processors.py' adding 'django/template/defaultfilters.py' adding 'django/template/defaulttags.py' adding 'django/template/engine.py' adding 'django/template/exceptions.py' adding 'django/template/library.py' adding 'django/template/loader.py' adding 'django/template/loader_tags.py' adding 'django/template/response.py' adding 'django/template/smartif.py' adding 'django/template/utils.py' adding 'django/template/backends/__init__.py' adding 'django/template/backends/base.py' adding 'django/template/backends/django.py' adding 'django/template/backends/dummy.py' adding 'django/template/backends/jinja2.py' adding 'django/template/backends/utils.py' adding 'django/template/loaders/__init__.py' adding 'django/template/loaders/app_directories.py' adding 'django/template/loaders/base.py' adding 'django/template/loaders/cached.py' adding 'django/template/loaders/filesystem.py' adding 'django/template/loaders/locmem.py' adding 'django/templatetags/__init__.py' adding 'django/templatetags/cache.py' adding 'django/templatetags/i18n.py' adding 'django/templatetags/l10n.py' adding 'django/templatetags/static.py' adding 'django/templatetags/tz.py' adding 'django/test/__init__.py' adding 'django/test/client.py' adding 'django/test/html.py' adding 'django/test/runner.py' adding 'django/test/selenium.py' adding 'django/test/signals.py' adding 'django/test/testcases.py' adding 'django/test/utils.py' adding 'django/urls/__init__.py' adding 'django/urls/base.py' adding 'django/urls/conf.py' adding 'django/urls/converters.py' adding 'django/urls/exceptions.py' adding 'django/urls/resolvers.py' adding 'django/urls/utils.py' adding 'django/utils/__init__.py' adding 'django/utils/_os.py' adding 'django/utils/archive.py' adding 'django/utils/asyncio.py' adding 'django/utils/autoreload.py' adding 'django/utils/baseconv.py' adding 'django/utils/cache.py' adding 'django/utils/connection.py' adding 'django/utils/crypto.py' adding 'django/utils/datastructures.py' adding 'django/utils/dateformat.py' adding 'django/utils/dateparse.py' adding 'django/utils/dates.py' adding 'django/utils/datetime_safe.py' adding 'django/utils/deconstruct.py' adding 'django/utils/decorators.py' adding 'django/utils/deprecation.py' adding 'django/utils/duration.py' adding 'django/utils/encoding.py' adding 'django/utils/feedgenerator.py' adding 'django/utils/formats.py' adding 'django/utils/functional.py' adding 'django/utils/hashable.py' adding 'django/utils/html.py' adding 'django/utils/http.py' adding 'django/utils/inspect.py' adding 'django/utils/ipv6.py' adding 'django/utils/itercompat.py' adding 'django/utils/jslex.py' adding 'django/utils/log.py' adding 'django/utils/lorem_ipsum.py' adding 'django/utils/module_loading.py' adding 'django/utils/numberformat.py' adding 'django/utils/regex_helper.py' adding 'django/utils/safestring.py' adding 'django/utils/termcolors.py' adding 'django/utils/text.py' adding 'django/utils/timesince.py' adding 'django/utils/timezone.py' adding 'django/utils/topological_sort.py' adding 'django/utils/tree.py' adding 'django/utils/version.py' adding 'django/utils/xmlutils.py' adding 'django/utils/translation/__init__.py' adding 'django/utils/translation/reloader.py' adding 'django/utils/translation/template.py' adding 'django/utils/translation/trans_null.py' adding 'django/utils/translation/trans_real.py' adding 'django/views/__init__.py' adding 'django/views/csrf.py' adding 'django/views/debug.py' adding 'django/views/defaults.py' adding 'django/views/i18n.py' adding 'django/views/static.py' adding 'django/views/decorators/__init__.py' adding 'django/views/decorators/cache.py' adding 'django/views/decorators/clickjacking.py' adding 'django/views/decorators/common.py' adding 'django/views/decorators/csrf.py' adding 'django/views/decorators/debug.py' adding 'django/views/decorators/gzip.py' adding 'django/views/decorators/http.py' adding 'django/views/decorators/vary.py' adding 'django/views/generic/__init__.py' adding 'django/views/generic/base.py' adding 'django/views/generic/dates.py' adding 'django/views/generic/detail.py' adding 'django/views/generic/edit.py' adding 'django/views/generic/list.py' adding 'django/views/templates/default_urlconf.html' adding 'django/views/templates/technical_404.html' adding 'django/views/templates/technical_500.html' adding 'django/views/templates/technical_500.txt' adding 'Django-4.2.5.dist-info/AUTHORS' adding 'Django-4.2.5.dist-info/LICENSE' adding 'Django-4.2.5.dist-info/LICENSE.python' adding 'Django-4.2.5.dist-info/METADATA' adding 'Django-4.2.5.dist-info/WHEEL' adding 'Django-4.2.5.dist-info/entry_points.txt' adding 'Django-4.2.5.dist-info/top_level.txt' adding 'Django-4.2.5.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Successfully built Django-4.2.5-py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase installing Executing pypaInstallPhase Successfully installed Django-4.2.5-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5 checking for references to /build/ in /nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5... patching script interpreter paths in /nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5 /nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5/lib/python3.10/site-packages/django/conf/project_template/manage.py-tpl: interpreter directive changed from "#!/usr/bin/env python" to "/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python" stripping (with command strip and flags -S -p) in /nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5/lib /nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5/bin shrinking RPATHs of ELF executables and libraries in /nix/store/2dwb91ddwzwrl7xsagnv7l1dbr82alfj-python3.10-Django-4.2.5-dist checking for references to /build/ in /nix/store/2dwb91ddwzwrl7xsagnv7l1dbr82alfj-python3.10-Django-4.2.5-dist... patching script interpreter paths in /nix/store/2dwb91ddwzwrl7xsagnv7l1dbr82alfj-python3.10-Django-4.2.5-dist Rewriting #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 to #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12 wrapping `/nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5/bin/django-admin'... Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests /build/Django-4.2.5/tests /build/Django-4.2.5 Testing against Django installed in '/nix/store/yxs2d8f17yyww6h66kxqg3nny6f1yvrj-python3.10-Django-4.2.5/lib/python3.10/site-packages/django' with up to 16 processes Found 16323 test(s). Creating test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Cloning test database for alias 'default'... Creating test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... Cloning test database for alias 'other'... System check identified no issues (17 silenced). *( ..............................................................................s.......................s...s...s......sss.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................s.......................................................................................s.......................s...........................................................................sss.ss..s.sssssss.......sssssssssssssssssssssssssssssssssssssssssssssss.........................s..............................................................sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss...............................ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss....ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss........ssssssssssssssssssssss.........sssssssssssss................ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss...............................s.........................................................................................................................................................................................................................................................................................................................................................................................................s....................................................................................................................................................................ss...............................................................................................................................................................sssssss.............................................................................................................................s...............................................................................................................................................s.....................................................................................................................................................................................................................................................................................................................................................................ss............s..s...................................................................................................................................................................................................................ssss................................................................................................................................................................s...s..........s..........s.s...................................................................................s.s...s...................................................s.s...............................................................................................................................................................s..s..s..s...................s.................................................................s........................................................................s..........................................................................................................x.................s...........................................................................................................................................................................................................................................................................................................................................................................................................................s.............................................................................................................................................................................................................................................................................................................................................s.....................................s...s............................................................s...................................ssss..........................................................s.s.s.................ss.sss.s....................s..........s........................................s..........ss.s.......................................................s.............................................ss......s.....................................................sss.............................................................................x......................s..x.........x........................................................s.s...............s.........................................s..............................................s.......................................................................................................................s....s....ss.....s....s......s..............sss...ss....................................................................................................................s................................................................................................................................................................................................................................................................s................................................................ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss..............................................................................s...................................................................................s...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................s...s.......s.........................................s.............ssss...................................ssss..............................................................................................................s......................................................................................................ss...............................................................................ssss.ssssssssssssssssssssssssssssss..............................................................................................sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss..ss.................................................................................................................................................sss............s.........................s............................................................................................................ssss.........................s.s................................................................ssssss..............................ssssssssss..............................ssssssssss..................................................................ssss....ss............................................................................................................s.................................................................................................................................................................................................................s.........s..s.................................................................................s..................................................................................................................................................................................................................................................................................................................................................................................................................................................................sssssssssssssss.........ssssssssssssssssssssssssssssssssssssssssssssssssssssssss........sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss...............sssss.............s................................................................................................ssssssssssssssssssss......................................................................................................................................................................................................................................................................................................................................................ssssssss.....s...s....................................................................................................................................................................................................................................................................................................ssssssssssssssssssss.s.sssss.ssssssss.............................................................................................................................................................................................................................s.s................................................................................................................................................................................................................ssssssssssss.........................................................................................................s.............s.......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................s..............................................................................................................................s....................................................................................................................................................................................s...................................................................................................s......sss............................................................s....................................................................................................................ss..............................sssssss..ssss....ss..................................................................................................................................................................................sssss.....ssssssssssss.................................................................................................................s........s..............sss...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................x..............................ss............................................................................................................................................................................................('127.0.0.1', 49316) unrecognised: # ...............................................................................................................................................................................................................................................................s............................................................................................................................................................................................................................................................................................................................................................................................................................ss.......................................................................................................................................................................................................................................ss............................s.....................................................................................................................................................................................................................................................................................................................................................................................s................s.........................................................................................................................................................................................................................................................................................................................s.ss...............sss...s.ss.....s.ss.ss.sss..s......ss.s.s.................s........s.....................ss..ss...................s..s....s...s.....................s...............s.......s...s...ss...............................s........................................................................................................................................................... ---------------------------------------------------------------------- Ran 16321 tests in 55.751s OK (skipped=1315, expected failures=5) Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'default'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... Destroying test database for alias 'other'... /build/Django-4.2.5 installCheckPhase completed in 1 minutes 13 seconds pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase building '/nix/store/pmq79nila8y4m8yzwnjblxf6zgi1rw5w-python3.10-factory-boy-3.3.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/hf6ncbp5w7xfiissfkywg4k6nn1zsnk3-factory_boy-3.3.0.tar.gz source root is factory_boy-3.3.0 setting SOURCE_DATE_EPOCH to timestamp 1689757437 of file factory_boy-3.3.0/setup.cfg patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/factory copying factory/helpers.py -> build/lib/factory copying factory/alchemy.py -> build/lib/factory copying factory/__init__.py -> build/lib/factory copying factory/enums.py -> build/lib/factory copying factory/base.py -> build/lib/factory copying factory/mogo.py -> build/lib/factory copying factory/builder.py -> build/lib/factory copying factory/declarations.py -> build/lib/factory copying factory/fuzzy.py -> build/lib/factory copying factory/faker.py -> build/lib/factory copying factory/mongoengine.py -> build/lib/factory copying factory/django.py -> build/lib/factory copying factory/errors.py -> build/lib/factory copying factory/random.py -> build/lib/factory copying factory/utils.py -> build/lib/factory /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/faker.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/__init__.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/fuzzy.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/alchemy.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/helpers.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/base.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/random.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/mogo.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/mongoengine.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/builder.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/errors.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/django.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/enums.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/utils.py -> build/bdist.linux-x86_64/wheel/factory copying build/lib/factory/declarations.py -> build/bdist.linux-x86_64/wheel/factory running install_egg_info running egg_info writing factory_boy.egg-info/PKG-INFO writing dependency_links to factory_boy.egg-info/dependency_links.txt writing requirements to factory_boy.egg-info/requires.txt writing top-level names to factory_boy.egg-info/top_level.txt reading manifest file 'factory_boy.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'readthedocs.yml' warning: no previously-included files matching '*.py[cod]' found anywhere in distribution warning: no previously-included files matching '__pycache__' found anywhere in distribution warning: no previously-included files matching '.*.sw[po]' found anywhere in distribution no previously-included directories found matching '.github' no previously-included directories found matching 'docs/_build' adding license file 'LICENSE' writing manifest file 'factory_boy.egg-info/SOURCES.txt' Copying factory_boy.egg-info to build/bdist.linux-x86_64/wheel/factory_boy-3.3.0-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/factory_boy-3.3.0.dist-info/WHEEL creating 'dist/factory_boy-3.3.0-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'factory/__init__.py' adding 'factory/alchemy.py' adding 'factory/base.py' adding 'factory/builder.py' adding 'factory/declarations.py' adding 'factory/django.py' adding 'factory/enums.py' adding 'factory/errors.py' adding 'factory/faker.py' adding 'factory/fuzzy.py' adding 'factory/helpers.py' adding 'factory/mogo.py' adding 'factory/mongoengine.py' adding 'factory/random.py' adding 'factory/utils.py' adding 'factory_boy-3.3.0.dist-info/LICENSE' adding 'factory_boy-3.3.0.dist-info/METADATA' adding 'factory_boy-3.3.0.dist-info/WHEEL' adding 'factory_boy-3.3.0.dist-info/top_level.txt' adding 'factory_boy-3.3.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed factory_boy-3.3.0-py2.py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/394b3my8cvhn1shc98yffjf7y94r0k1g-python3.10-factory-boy-3.3.0 checking for references to /build/ in /nix/store/394b3my8cvhn1shc98yffjf7y94r0k1g-python3.10-factory-boy-3.3.0... patching script interpreter paths in /nix/store/394b3my8cvhn1shc98yffjf7y94r0k1g-python3.10-factory-boy-3.3.0 stripping (with command strip and flags -S -p) in /nix/store/394b3my8cvhn1shc98yffjf7y94r0k1g-python3.10-factory-boy-3.3.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/9540gqd481qa9f8cbidpijqc4p6q665n-python3.10-factory-boy-3.3.0-dist checking for references to /build/ in /nix/store/9540gqd481qa9f8cbidpijqc4p6q665n-python3.10-factory-boy-3.3.0-dist... patching script interpreter paths in /nix/store/9540gqd481qa9f8cbidpijqc4p6q665n-python3.10-factory-boy-3.3.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: factory pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/factory_boy-3.3.0 plugins: Faker-17.3.0 collected 436 items / 2 deselected / 434 selected tests/test_alchemy.py ......................... [ 5%] tests/test_base.py .................................... [ 14%] tests/test_declarations.py ............................... [ 21%] tests/test_dev_experience.py .. [ 21%] tests/test_django.py ................................................... [ 33%] sssssssssssssss................ [ 40%] tests/test_docs_internals.py . [ 40%] tests/test_faker.py ..... [ 41%] tests/test_fuzzy.py .................................................... [ 53%] .......... [ 56%] tests/test_helpers.py ... [ 56%] tests/test_regression.py . [ 57%] tests/test_transformer.py ................. [ 61%] tests/test_using.py .................................................... [ 73%] ........................................................................ [ 89%] ......................... [ 95%] tests/test_utils.py ................... [ 99%] tests/test_version.py . [100%] =============================== warnings summary =============================== tests/test_base.py:8 /build/factory_boy-3.3.0/tests/test_base.py:8: PytestCollectionWarning: cannot collect test class 'TestObject' because it has a __init__ constructor (from: tests/test_base.py) class TestObject: tests/test_base.py:38 /build/factory_boy-3.3.0/tests/test_base.py:38: PytestCollectionWarning: cannot collect test class 'TestModel' because it has a __init__ constructor (from: tests/test_base.py) class TestModel(FakeDjangoModel): tests/test_transformer.py:86 /build/factory_boy-3.3.0/tests/test_transformer.py:86: PytestCollectionWarning: cannot collect test class 'TestObject' because it has a __init__ constructor (from: tests/test_transformer.py) class TestObject: tests/test_using.py:24 /build/factory_boy-3.3.0/tests/test_using.py:24: PytestCollectionWarning: cannot collect test class 'TestObject' because it has a __init__ constructor (from: tests/test_using.py) class TestObject: tests/test_using.py:107 /build/factory_boy-3.3.0/tests/test_using.py:107: PytestCollectionWarning: cannot collect test class 'TestModel' because it has a __init__ constructor (from: tests/test_using.py) class TestModel(FakeModel): -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ========== 419 passed, 15 skipped, 2 deselected, 5 warnings in 4.18s =========== Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/1644v1yqzzg66f88y08ppz5ajnxa88pm-python3.10-pytest-randomly-3.13.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing pytest-check-hook Using pytestCheckPhase unpacking sources unpacking source archive /nix/store/1ni18mfnmw0m25ikhmikbmg33r4ywnq5-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tox.ini patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing pypaBuildPhase Creating a wheel... * Getting build dependencies for wheel... running egg_info creating src/pytest_randomly.egg-info writing src/pytest_randomly.egg-info/PKG-INFO writing dependency_links to src/pytest_randomly.egg-info/dependency_links.txt writing entry points to src/pytest_randomly.egg-info/entry_points.txt writing requirements to src/pytest_randomly.egg-info/requires.txt writing top-level names to src/pytest_randomly.egg-info/top_level.txt writing manifest file 'src/pytest_randomly.egg-info/SOURCES.txt' reading manifest file 'src/pytest_randomly.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/pytest_randomly.egg-info/SOURCES.txt' * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/pytest_randomly copying src/pytest_randomly/__init__.py -> build/lib/pytest_randomly copying src/pytest_randomly/compat.py -> build/lib/pytest_randomly running egg_info writing src/pytest_randomly.egg-info/PKG-INFO writing dependency_links to src/pytest_randomly.egg-info/dependency_links.txt writing entry points to src/pytest_randomly.egg-info/entry_points.txt writing requirements to src/pytest_randomly.egg-info/requires.txt writing top-level names to src/pytest_randomly.egg-info/top_level.txt reading manifest file 'src/pytest_randomly.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'src/pytest_randomly.egg-info/SOURCES.txt' copying src/pytest_randomly/py.typed -> build/lib/pytest_randomly installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/pytest_randomly copying build/lib/pytest_randomly/compat.py -> build/bdist.linux-x86_64/wheel/pytest_randomly copying build/lib/pytest_randomly/__init__.py -> build/bdist.linux-x86_64/wheel/pytest_randomly copying build/lib/pytest_randomly/py.typed -> build/bdist.linux-x86_64/wheel/pytest_randomly running install_egg_info Copying src/pytest_randomly.egg-info to build/bdist.linux-x86_64/wheel/pytest_randomly-3.13.0-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/pytest_randomly-3.13.0.dist-info/WHEEL creating '/build/source/dist/.tmp-o317gx9l/pytest_randomly-3.13.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'pytest_randomly/__init__.py' adding 'pytest_randomly/compat.py' adding 'pytest_randomly/py.typed' adding 'pytest_randomly-3.13.0.dist-info/LICENSE' adding 'pytest_randomly-3.13.0.dist-info/METADATA' adding 'pytest_randomly-3.13.0.dist-info/WHEEL' adding 'pytest_randomly-3.13.0.dist-info/entry_points.txt' adding 'pytest_randomly-3.13.0.dist-info/top_level.txt' adding 'pytest_randomly-3.13.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Successfully built pytest_randomly-3.13.0-py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase installing Executing pypaInstallPhase Successfully installed pytest_randomly-3.13.0-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/z23gg1yjq1snc2cmkacik9kn9ajfx1fp-python3.10-pytest-randomly-3.13.0 checking for references to /build/ in /nix/store/z23gg1yjq1snc2cmkacik9kn9ajfx1fp-python3.10-pytest-randomly-3.13.0... patching script interpreter paths in /nix/store/z23gg1yjq1snc2cmkacik9kn9ajfx1fp-python3.10-pytest-randomly-3.13.0 stripping (with command strip and flags -S -p) in /nix/store/z23gg1yjq1snc2cmkacik9kn9ajfx1fp-python3.10-pytest-randomly-3.13.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/fgmxdw21n9sm22wp9ip5jrhza87x4y83-python3.10-pytest-randomly-3.13.0-dist checking for references to /build/ in /nix/store/fgmxdw21n9sm22wp9ip5jrhza87x4y83-python3.10-pytest-randomly-3.13.0-dist... patching script interpreter paths in /nix/store/fgmxdw21n9sm22wp9ip5jrhza87x4y83-python3.10-pytest-randomly-3.13.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: pytest_randomly pytestXdistHook pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/source configfile: pyproject.toml plugins: Faker-17.3.0, xdist-3.3.1 16 workers [36 items] m .................................... [100%] ============================== 36 passed in 5.13s ============================== Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/81q5zh3i7ivm31qyq334l0lz6k850pza-python3.10-httplib2-0.21.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing setuptools-check-hook Using setuptoolsCheckPhase Sourcing pytest-check-hook Using pytestCheckPhase Removing setuptoolsCheckPhase unpacking sources unpacking source archive /nix/store/w5aclspb1adjpdnz16bpl8vbngj2s5jc-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/tests/tls/server_chain.pem patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/httplib2 copying python3/httplib2/certs.py -> build/lib/httplib2 copying python3/httplib2/error.py -> build/lib/httplib2 copying python3/httplib2/auth.py -> build/lib/httplib2 copying python3/httplib2/socks.py -> build/lib/httplib2 copying python3/httplib2/iri2uri.py -> build/lib/httplib2 copying python3/httplib2/__init__.py -> build/lib/httplib2 copying python3/httplib2/cacerts.txt -> build/lib/httplib2 /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/httplib2 copying build/lib/httplib2/cacerts.txt -> build/bdist.linux-x86_64/wheel/httplib2 copying build/lib/httplib2/error.py -> build/bdist.linux-x86_64/wheel/httplib2 copying build/lib/httplib2/auth.py -> build/bdist.linux-x86_64/wheel/httplib2 copying build/lib/httplib2/certs.py -> build/bdist.linux-x86_64/wheel/httplib2 copying build/lib/httplib2/__init__.py -> build/bdist.linux-x86_64/wheel/httplib2 copying build/lib/httplib2/iri2uri.py -> build/bdist.linux-x86_64/wheel/httplib2 copying build/lib/httplib2/socks.py -> build/bdist.linux-x86_64/wheel/httplib2 running install_egg_info running egg_info creating python3/httplib2.egg-info writing python3/httplib2.egg-info/PKG-INFO writing dependency_links to python3/httplib2.egg-info/dependency_links.txt writing requirements to python3/httplib2.egg-info/requires.txt writing top-level names to python3/httplib2.egg-info/top_level.txt writing manifest file 'python3/httplib2.egg-info/SOURCES.txt' reading manifest file 'python3/httplib2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'codecov.yml' warning: no previously-included files found matching '.pre-commit-*.yaml' no previously-included directories found matching 'ref' warning: no previously-included files matching '__pycache__' found anywhere in distribution warning: no previously-included files matching '*.py[cod]' found anywhere in distribution adding license file 'LICENSE' writing manifest file 'python3/httplib2.egg-info/SOURCES.txt' Copying python3/httplib2.egg-info to build/bdist.linux-x86_64/wheel/httplib2-0.21.0-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/httplib2-0.21.0.dist-info/WHEEL creating 'dist/httplib2-0.21.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'httplib2/__init__.py' adding 'httplib2/auth.py' adding 'httplib2/cacerts.txt' adding 'httplib2/certs.py' adding 'httplib2/error.py' adding 'httplib2/iri2uri.py' adding 'httplib2/socks.py' adding 'httplib2-0.21.0.dist-info/LICENSE' adding 'httplib2-0.21.0.dist-info/METADATA' adding 'httplib2-0.21.0.dist-info/WHEEL' adding 'httplib2-0.21.0.dist-info/top_level.txt' adding 'httplib2-0.21.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed httplib2-0.21.0-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/zz890d6wsk38324nr1jz83zb7pidjfc8-python3.10-httplib2-0.21.0 checking for references to /build/ in /nix/store/zz890d6wsk38324nr1jz83zb7pidjfc8-python3.10-httplib2-0.21.0... patching script interpreter paths in /nix/store/zz890d6wsk38324nr1jz83zb7pidjfc8-python3.10-httplib2-0.21.0 stripping (with command strip and flags -S -p) in /nix/store/zz890d6wsk38324nr1jz83zb7pidjfc8-python3.10-httplib2-0.21.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/0mnn3dw2hnv95zqdqv3pj6bzhks3pw98-python3.10-httplib2-0.21.0-dist checking for references to /build/ in /nix/store/0mnn3dw2hnv95zqdqv3pj6bzhks3pw98-python3.10-httplib2-0.21.0-dist... patching script interpreter paths in /nix/store/0mnn3dw2hnv95zqdqv3pj6bzhks3pw98-python3.10-httplib2-0.21.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: httplib2 pytestForkedHook pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 -- /nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 cachedir: .pytest_cache Using --randomly-seed=2736606886 rootdir: /build/source configfile: setup.cfg plugins: forked-1.6.0, randomly-3.13.0, timeout-2.1.0 timeout: 17.0s timeout method: signal timeout func_only: False collected 493 items / 3 deselected / 490 selected tests/test_proxy.py::test_noproxy_trailing_comma PASSED [ 0%] tests/test_proxy.py::test_from_url_ident PASSED [ 0%] tests/test_proxy.py::test_proxy_info_repr PASSED [ 0%] tests/test_proxy.py::test_auth_str_bytes PASSED [ 0%] tests/test_proxy.py::test_server_not_found_error_is_raised_for_invalid_hostname PASSED [ 1%] tests/test_proxy.py::test_from_env_https PASSED [ 1%] tests/test_proxy.py::test_noproxy_star PASSED [ 1%] tests/test_proxy.py::test_from_url_ipv6 PASSED [ 1%] tests/test_proxy.py::test_functional_noproxy_star_https PASSED [ 1%] tests/test_proxy.py::test_from_url PASSED [ 2%] tests/test_proxy.py::test_from_env_other PASSED [ 2%] tests/test_proxy.py::test_from_env PASSED [ 2%] tests/test_proxy.py::test_functional_noproxy_star_http PASSED [ 2%] tests/test_proxy.py::test_socks5_auth PASSED [ 2%] tests/test_proxy.py::test_applies_to PASSED [ 3%] tests/test_proxy.py::test_headers PASSED [ 3%] tests/test_proxy.py::test_from_env_none PASSED [ 3%] tests/test_proxy.py::test_from_url_no_password PASSED [ 3%] tests/test_auth.py::test_basic PASSED [ 3%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Test realm="a \\\\"test\\\\" realm"'}] PASSED [ 4%] tests/test_auth.py::test_wsse_algorithm PASSED [ 4%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'T*!%#st realm=to*!%#en, to*!%#en="quoted string"'}] PASSED [ 4%] tests/test_auth.py::test_parse_www_authenticate_complexity PASSED [ 4%] tests/test_auth.py::test_digest PASSED [ 4%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Basic realm="me", algorithm="MD5"'}] PASSED [ 5%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Basic realm="me", algorithm=MD5'}] PASSED [ 5%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Digest realm="2-comma-d", qop="auth-int", nonce="c0c8ff1", Basic realm="2-comma-b"'}] PASSED [ 5%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Basic REAlm="me" '}] PASSED [ 5%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Basic realm="me", algorithm=MD5'}] PASSED [ 5%] tests/test_auth.py::test_wsse_invalid PASSED [ 6%] tests/test_auth.py::test_benchmark_parse_www_authenticate[Digest realm="2-comma-d", qop="auth-int", nonce="c0c8ff1", Basic realm="2-comma-b"] SKIPPED [ 6%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': ''}] PASSED [ 6%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Digest realm="com3d", Basic realm="com3b", WSSE realm="com3w", profile="token"'}] PASSED [ 6%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Basic realm="me",other="fred" '}] PASSED [ 6%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Digest realm="2-comma-d", qop="auth-int", nonce="c0c8ff1", Basic realm="2-comma-b"'}] PASSED [ 7%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Digest realm="digest1", qop="auth,auth-int", nonce="7102dd2", opaque="e9517f"'}] PASSED [ 7%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'T*!%#st realm=to*!%#en, to*!%#en="quoted string"'}] PASSED [ 7%] tests/test_auth.py::test_digest_object_stale PASSED [ 7%] tests/test_auth.py::test_digest_object PASSED [ 7%] tests/test_auth.py::test_benchmark_parse_www_authenticate[Digest realm="digest1", qop="auth,auth-int", nonce="7102dd2", opaque="e9517f"] SKIPPED [ 8%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{}] PASSED [ 8%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Basic realm="me"'}] PASSED [ 8%] tests/test_auth.py::test_benchmark_parse_www_authenticate[Bearer 0b79bab50daca910b000d4f1a2b675d604257e42] SKIPPED [ 8%] tests/test_auth.py::test_basic_for_domain PASSED [ 8%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': "Basic param='single quote'"}] PASSED [ 9%] tests/test_auth.py::test_parse_www_authenticate_malformed[{'www-authenticate': 'OAuth "Facebook Platform" "invalid_token" "Invalid OAuth access token."'}] PASSED [ 9%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Basic realm="me",other="fred" '}] PASSED [ 9%] tests/test_auth.py::test_wsse_ok PASSED [ 9%] tests/test_auth.py::test_digest_object_with_opaque PASSED [ 10%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': "Basic param='single quote'"}] PASSED [ 10%] tests/test_auth.py::test_credentials PASSED [ 10%] tests/test_auth.py::test_digest_auth_stale PASSED [ 10%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Basic REAlm="me" '}] PASSED [ 10%] tests/test_auth.py::test_basic_two_credentials PASSED [ 11%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Digest realm="myrealm", nonce="KBAA=3", algorithm=MD5, qop="auth", stale=true'}] PASSED [ 11%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Test realm="a \\\\"test\\\\" realm"'}] PASSED [ 11%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Test realm="test realm" , foo=foo ,bar="bar", baz=baz,qux=qux'}] PASSED [ 11%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{}] PASSED [ 11%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Digest realm="myrealm", nonce="KBAA=3", algorithm=MD5, qop="auth", stale=true'}] PASSED [ 12%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Basic realm="me", algorithm="MD5"'}] PASSED [ 12%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Digest realm="com3d", Basic realm="com3b", WSSE realm="com3w", profile="token"'}] PASSED [ 12%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Test realm="test realm" , foo=foo ,bar="bar", baz=baz,qux=qux'}] PASSED [ 12%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': 'Digest realm="digest1", qop="auth,auth-int", nonce="7102dd2", opaque="e9517f"'}] PASSED [ 12%] tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate': 'Basic realm="me"'}] PASSED [ 13%] tests/test_auth.py::test_digest_object_auth_info PASSED [ 13%] tests/test_auth.py::test_benchmark_parse_www_authenticate[Basic realm="me", algorithm="MD5"] SKIPPED [ 13%] tests/test_auth.py::test_digest_next_nonce_nc PASSED [ 13%] tests/test_auth.py::test_parse_www_authenticate_correct[relax-{'www-authenticate': ''}] PASSED [ 13%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=[fe80::1]-port=_-path=/] PASSED [ 14%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=fqdn.-port=81-path=_] PASSED [ 14%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=fqdn.-port=81-path=_] PASSED [ 14%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=[fe80::1]-port=81-path=_] PASSED [ 14%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=[fe80::1]-port=_-path=_] PASSED [ 14%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=_-port=81-path=/] PASSED [ 15%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=1.1.1.1-port=81-path=_] PASSED [ 15%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=_-port=_-path=/] PASSED [ 15%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=_-port=None-path=/] PASSED [ 15%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=[fe80::1]-port=81-path=_] PASSED [ 15%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=fqdn.-port=81-path=/] PASSED [ 16%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=_-port=_-path=/] PASSED [ 16%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=[fe80::1]-port=_-path=/] PASSED [ 16%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=_-port=_-path=_] PASSED [ 16%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=_-port=None-path=_] PASSED [ 16%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=1.1.1.1-port=_-path=_] PASSED [ 17%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=fqdn.-port=81-path=/] PASSED [ 17%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=fqdn.-port=81-path=_] PASSED [ 17%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=[fe80::1]-port=81-path=/] PASSED [ 17%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=1.1.1.1-port=81-path=_] PASSED [ 17%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=[fe80::1]-port=_-path=/] PASSED [ 18%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=fqdn.-port=81-path=_] PASSED [ 18%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=1.1.1.1-port=81-path=/] PASSED [ 18%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=1.1.1.1-port=81-path=_] PASSED [ 18%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=_-port=81-path=_] PASSED [ 18%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=_-port=81-path=/] PASSED [ 19%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=_-port=_-path=_] PASSED [ 19%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=_-port=81-path=/] PASSED [ 19%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=fqdn.-port=_-path=_] PASSED [ 19%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=fqdn.-port=None-path=/] PASSED [ 20%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=fqdn.-port=_-path=/] PASSED [ 20%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=1.1.1.1-port=None-path=/] PASSED [ 20%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=1.1.1.1-port=_-path=_] PASSED [ 20%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=1.1.1.1-port=None-path=_] PASSED [ 20%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=[fe80::1]-port=_-path=_] PASSED [ 21%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=1.1.1.1-port=81-path=/] PASSED [ 21%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=fqdn.-port=_-path=/] PASSED [ 21%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=[fe80::1]-port=81-path=/] PASSED [ 21%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=_-port=_-path=_] PASSED [ 21%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=1.1.1.1-port=_-path=/] PASSED [ 22%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=1.1.1.1-port=81-path=/] PASSED [ 22%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=_-port=None-path=_] PASSED [ 22%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=fqdn.-port=_-path=/] PASSED [ 22%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=_-port=None-path=/] PASSED [ 22%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=_-port=_-path=_] PASSED [ 23%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=_-port=None-path=_] PASSED [ 23%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=1.1.1.1-port=81-path=_] PASSED [ 23%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=[fe80::1]-port=81-path=/] PASSED [ 23%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=_-port=None-path=/] PASSED [ 23%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=1.1.1.1-port=_-path=/] PASSED [ 24%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=[fe80::1]-port=_-path=_] PASSED [ 24%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=fqdn.-port=_-path=/] PASSED [ 24%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=[fe80::1]-port=_-path=_] PASSED [ 24%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=fqdn.-port=81-path=_] PASSED [ 24%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=fqdn.-port=_-path=_] PASSED [ 25%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=fqdn.-port=None-path=/] PASSED [ 25%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=1.1.1.1-port=_-path=/] PASSED [ 25%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=_-port=81-path=/] PASSED [ 25%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=1.1.1.1-port=81-path=/] PASSED [ 25%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=_-port=81-path=_] PASSED [ 26%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=fqdn.-port=81-path=/] PASSED [ 26%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=_-port=None-path=_] PASSED [ 26%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=1.1.1.1-port=81-path=/] PASSED [ 26%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=_-port=None-path=_] PASSED [ 26%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=_-port=None-path=_] PASSED [ 27%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=fqdn.-port=None-path=/] PASSED [ 27%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=fqdn.-port=None-path=_] PASSED [ 27%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=1.1.1.1-port=_-path=_] PASSED [ 27%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=1.1.1.1-port=_-path=_] PASSED [ 27%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=1.1.1.1-port=None-path=/] PASSED [ 28%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=[fe80::1]-port=None-path=_] PASSED [ 28%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=_-port=81-path=_] PASSED [ 28%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=[fe80::1]-port=None-path=_] PASSED [ 28%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=1.1.1.1-port=None-path=_] PASSED [ 28%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=[fe80::1]-port=None-path=/] PASSED [ 29%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=1.1.1.1-port=None-path=/] PASSED [ 29%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=1.1.1.1-port=_-path=_] PASSED [ 29%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=1.1.1.1-port=_-path=/] PASSED [ 29%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=[fe80::1]-port=None-path=_] PASSED [ 30%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=_-port=None-path=/] PASSED [ 30%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=[fe80::1]-port=_-path=/] PASSED [ 30%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=1.1.1.1-port=_-path=/] PASSED [ 30%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=[fe80::1]-port=_-path=/] PASSED [ 30%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=fqdn.-port=81-path=/] PASSED [ 31%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=fqdn.-port=81-path=/] PASSED [ 31%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=[fe80::1]-port=_-path=_] PASSED [ 31%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=_-port=81-path=/] PASSED [ 31%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=[fe80::1]-port=None-path=/] PASSED [ 31%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=[fe80::1]-port=81-path=_] PASSED [ 32%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=1.1.1.1-port=81-path=_] PASSED [ 32%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=_-port=_-path=/] PASSED [ 32%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=[fe80::1]-port=_-path=/] PASSED [ 32%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=1.1.1.1-port=_-path=_] PASSED [ 32%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=1.1.1.1-port=None-path=_] PASSED [ 33%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=[fe80::1]-port=81-path=/] PASSED [ 33%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=fqdn.-port=_-path=_] PASSED [ 33%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=[fe80::1]-port=81-path=/] PASSED [ 33%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=fqdn.-port=_-path=/] PASSED [ 33%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=fqdn.-port=81-path=/] PASSED [ 34%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=[fe80::1]-port=_-path=_] PASSED [ 34%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=_-port=None-path=/] PASSED [ 34%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=[fe80::1]-port=81-path=_] PASSED [ 34%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=[fe80::1]-port=None-path=_] PASSED [ 34%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=fqdn.-port=81-path=_] PASSED [ 35%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=_-port=None-path=/] PASSED [ 35%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=_-port=81-path=/] PASSED [ 35%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=[fe80::1]-port=_-path=/] PASSED [ 35%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=fqdn.-port=None-path=/] PASSED [ 35%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=fqdn.-port=None-path=/] PASSED [ 36%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=[fe80::1]-port=_-path=/] PASSED [ 36%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=[fe80::1]-port=_-path=/] PASSED [ 36%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=1.1.1.1-port=81-path=/] PASSED [ 36%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=_-port=81-path=/] PASSED [ 36%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=[fe80::1]-port=81-path=_] PASSED [ 37%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=_-port=None-path=_] PASSED [ 37%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=_-port=None-path=/] PASSED [ 37%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=1.1.1.1-port=_-path=/] PASSED [ 37%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=_-port=_-path=_] PASSED [ 37%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=1.1.1.1-port=81-path=/] PASSED [ 38%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=1.1.1.1-port=None-path=_] PASSED [ 38%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=_-port=_-path=/] PASSED [ 38%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=_-port=_-path=/] PASSED [ 38%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=[fe80::1]-port=None-path=/] PASSED [ 38%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=fqdn.-port=81-path=_] PASSED [ 39%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=[fe80::1]-port=None-path=_] PASSED [ 39%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=1.1.1.1-port=None-path=/] PASSED [ 39%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=_-port=81-path=_] PASSED [ 39%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=[fe80::1]-port=None-path=_] PASSED [ 40%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=1.1.1.1-port=81-path=_] PASSED [ 40%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=1.1.1.1-port=81-path=_] PASSED [ 40%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=_-port=81-path=_] PASSED [ 40%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=fqdn.-port=None-path=_] PASSED [ 40%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=1.1.1.1-port=None-path=_] PASSED [ 41%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=_-port=81-path=_] PASSED [ 41%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=[fe80::1]-port=81-path=_] PASSED [ 41%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=[fe80::1]-port=None-path=/] PASSED [ 41%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=_-port=_-path=_] PASSED [ 41%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=fqdn.-port=81-path=/] PASSED [ 42%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=_-port=_-path=/] PASSED [ 42%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=1.1.1.1-port=_-path=_] PASSED [ 42%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=[fe80::1]-port=_-path=_] PASSED [ 42%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=1.1.1.1-port=None-path=_] PASSED [ 42%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=_-port=None-path=/] PASSED [ 43%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=1.1.1.1-port=_-path=_] PASSED [ 43%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=fqdn.-port=_-path=_] PASSED [ 43%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=1.1.1.1-port=None-path=_] PASSED [ 43%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=_-port=_-path=_] PASSED [ 43%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=[fe80::1]-port=81-path=_] PASSED [ 44%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=[fe80::1]-port=81-path=/] PASSED [ 44%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=_-port=None-path=/] PASSED [ 44%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=[fe80::1]-port=81-path=/] PASSED [ 44%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=fqdn.-port=_-path=/] PASSED [ 44%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=[fe80::1]-port=81-path=_] PASSED [ 45%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=[fe80::1]-port=81-path=/] PASSED [ 45%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=_-port=_-path=/] PASSED [ 45%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=fqdn.-port=None-path=/] PASSED [ 45%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=_-port=81-path=_] PASSED [ 45%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=fqdn.-port=None-path=/] PASSED [ 46%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=_-port=_-path=_] PASSED [ 46%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=fqdn.-port=None-path=_] PASSED [ 46%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=[fe80::1]-port=81-path=_] PASSED [ 46%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=fqdn.-port=81-path=_] PASSED [ 46%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=[fe80::1]-port=_-path=/] PASSED [ 47%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=fqdn.-port=None-path=/] PASSED [ 47%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=[fe80::1]-port=81-path=/] PASSED [ 47%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=fqdn.-port=None-path=_] PASSED [ 47%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=_-port=81-path=_] PASSED [ 47%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=[fe80::1]-port=None-path=/] PASSED [ 48%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=1.1.1.1-port=None-path=/] PASSED [ 48%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=_-port=None-path=_] PASSED [ 48%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=_-port=_-path=/] PASSED [ 48%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=_-port=_-path=_] PASSED [ 48%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=1.1.1.1-port=None-path=_] PASSED [ 49%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=fqdn.-port=_-path=/] PASSED [ 49%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=_-port=81-path=/] PASSED [ 49%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=1.1.1.1-port=None-path=_] PASSED [ 49%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=_-port=81-path=/] PASSED [ 50%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=[fe80::1]-port=81-path=_] PASSED [ 50%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=fqdn.-port=81-path=/] PASSED [ 50%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=1.1.1.1-port=81-path=/] PASSED [ 50%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=1.1.1.1-port=81-path=_] PASSED [ 50%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=1.1.1.1-port=_-path=/] PASSED [ 51%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=1.1.1.1-port=_-path=_] PASSED [ 51%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=[fe80::1]-port=_-path=/] PASSED [ 51%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=fqdn.-port=_-path=/] PASSED [ 51%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=1.1.1.1-port=81-path=_] PASSED [ 51%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=_-port=_-path=/] PASSED [ 52%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=1.1.1.1-port=81-path=_] PASSED [ 52%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=fqdn.-port=_-path=_] PASSED [ 52%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=fqdn.-port=81-path=_] PASSED [ 52%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=[fe80::1]-port=None-path=/] PASSED [ 52%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=fqdn.-port=None-path=_] PASSED [ 53%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=fqdn.-port=_-path=/] PASSED [ 53%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=1.1.1.1-port=None-path=/] PASSED [ 53%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=1.1.1.1-port=81-path=/] PASSED [ 53%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=[fe80::1]-port=_-path=_] PASSED [ 53%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=[fe80::1]-port=None-path=/] PASSED [ 54%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=_-port=_-path=_] PASSED [ 54%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=[fe80::1]-port=None-path=_] PASSED [ 54%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=1.1.1.1-port=_-path=/] PASSED [ 54%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=[fe80::1]-port=81-path=_] PASSED [ 54%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=fqdn.-port=81-path=_] PASSED [ 55%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=_-port=81-path=_] PASSED [ 55%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=fqdn.-port=_-path=/] PASSED [ 55%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=fqdn.-port=81-path=_] PASSED [ 55%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=[fe80::1]-port=None-path=_] PASSED [ 55%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=_-port=81-path=_] PASSED [ 56%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=fqdn.-port=None-path=_] PASSED [ 56%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=[fe80::1]-port=_-path=_] PASSED [ 56%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=[fe80::1]-port=None-path=/] PASSED [ 56%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=1.1.1.1-port=None-path=_] PASSED [ 56%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=_-port=81-path=/] PASSED [ 57%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=[fe80::1]-port=None-path=/] PASSED [ 57%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=fqdn.-port=_-path=_] PASSED [ 57%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=1.1.1.1-port=None-path=/] PASSED [ 57%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=1.1.1.1-port=_-path=_] PASSED [ 57%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=1.1.1.1-port=_-path=/] PASSED [ 58%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=fqdn.-port=_-path=_] PASSED [ 58%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=1.1.1.1-port=None-path=_] PASSED [ 58%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=fqdn.-port=None-path=/] PASSED [ 58%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=1.1.1.1-port=_-path=/] PASSED [ 58%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=1.1.1.1-port=81-path=_] PASSED [ 59%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=[fe80::1]-port=None-path=_] PASSED [ 59%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=fqdn.-port=_-path=_] PASSED [ 59%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=_-port=None-path=_] PASSED [ 59%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=[fe80::1]-port=81-path=/] PASSED [ 60%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=_-port=81-path=/] PASSED [ 60%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=[fe80::1]-port=None-path=/] PASSED [ 60%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=1.1.1.1-port=None-path=/] PASSED [ 60%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=1.1.1.1-port=_-path=_] PASSED [ 60%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=[fe80::1]-port=None-path=_] PASSED [ 61%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=fqdn.-port=_-path=_] PASSED [ 61%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=fqdn.-port=81-path=/] PASSED [ 61%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=fqdn.-port=_-path=/] PASSED [ 61%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=[fe80::1]-port=_-path=_] PASSED [ 61%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=[fe80::1]-port=None-path=_] PASSED [ 62%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=fqdn.-port=None-path=_] PASSED [ 62%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=fqdn.-port=81-path=/] PASSED [ 62%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=1.1.1.1-port=81-path=/] PASSED [ 62%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=[fe80::1]-port=_-path=_] PASSED [ 62%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=_-port=None-path=_] PASSED [ 63%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=[fe80::1]-port=None-path=/] PASSED [ 63%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=[fe80::1]-port=_-path=/] PASSED [ 63%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=fqdn.-port=81-path=_] PASSED [ 63%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=fqdn.-port=81-path=/] PASSED [ 63%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=1.1.1.1-port=_-path=/] PASSED [ 64%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=1.1.1.1-port=None-path=/] PASSED [ 64%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=random-host=_-port=None-path=_] PASSED [ 64%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=fqdn.-port=None-path=_] PASSED [ 64%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=1.1.1.1-port=None-path=/] PASSED [ 64%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=_-port=_-path=_] PASSED [ 65%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=_-port=None-path=/] PASSED [ 65%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=_-port=_-path=/] PASSED [ 65%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=[fe80::1]-port=_-path=_] PASSED [ 65%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=_-port=_-path=/] PASSED [ 65%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=fqdn.-port=None-path=_] PASSED [ 66%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=1.1.1.1-port=81-path=_] PASSED [ 66%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=_-port=None-path=/] PASSED [ 66%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=1.1.1.1-port=_-path=_] PASSED [ 66%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=fqdn.-port=81-path=/] PASSED [ 66%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=_-port=_-path=_] PASSED [ 67%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=random-host=[fe80::1]-port=81-path=_] PASSED [ 67%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=1.1.1.1-port=None-path=/] PASSED [ 67%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=fqdn.-port=_-path=/] PASSED [ 67%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=fqdn.-port=_-path=_] PASSED [ 67%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=[fe80::1]-port=None-path=/] PASSED [ 68%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=[fe80::1]-port=81-path=/] PASSED [ 68%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=fqdn.-port=None-path=_] PASSED [ 68%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=fqdn.-port=None-path=/] PASSED [ 68%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=_-port=81-path=/] PASSED [ 68%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=http-host=fqdn.-port=_-path=_] PASSED [ 69%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=[fe80::1]-port=81-path=/] PASSED [ 69%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=_-host=1.1.1.1-port=None-path=_] PASSED [ 69%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=1.1.1.1-port=81-path=/] PASSED [ 69%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=1.1.1.1-port=81-path=/] PASSED [ 70%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=[fe80::1]-port=None-path=_] PASSED [ 70%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=http-host=fqdn.-port=None-path=/] PASSED [ 70%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=https-host=_-port=81-path=_] PASSED [ 70%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=_-port=81-path=_] PASSED [ 70%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=fqdn.-port=None-path=/] PASSED [ 71%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=fqdn.-port=None-path=_] PASSED [ 71%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=random-host=_-port=None-path=/] PASSED [ 71%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=1.1.1.1-port=None-path=/] PASSED [ 71%] tests/test_test_helpers.py::test_rebuild_uri[base=//[::1]/path1-scheme=https-host=_-port=None-path=_] PASSED [ 71%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=https-host=fqdn.-port=None-path=_] PASSED [ 72%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=http-host=1.1.1.1-port=_-path=/] PASSED [ 72%] tests/test_test_helpers.py::test_rebuild_uri[base=127.0.0.1:8001-scheme=_-host=_-port=_-path=/] PASSED [ 72%] tests/test_test_helpers.py::test_rebuild_uri[base=https://foo.bar:8443/p?query-scheme=_-host=fqdn.-port=_-path=_] PASSED [ 72%] tests/test_encoding.py::test_deflate_get PASSED [ 72%] tests/test_encoding.py::test_gzip_get PASSED [ 73%] tests/test_encoding.py::test_zlib_get PASSED [ 73%] tests/test_encoding.py::test_gzip_post_response PASSED [ 73%] tests/test_encoding.py::test_gzip_head PASSED [ 73%] tests/test_encoding.py::test_gzip_malformed_response PASSED [ 73%] tests/test_encoding.py::test_deflate_malformed_response PASSED [ 74%] tests/test_cache.py::test_entry_disposition[({'cache-control': 'no-cache'}, {'cache-control': 'max-age=7200'}, 'TRANSPARENT')] PASSED [ 74%] tests/test_cache.py::test_expiration_model_date_and_expires PASSED [ 74%] tests/test_cache.py::test_get_cache_control_no_cache PASSED [ 74%] tests/test_cache.py::test_TODO_vary_no SKIPPED (was commented in leg...) [ 74%] tests/test_cache.py::test_update_uses_cached_etag[PUT] PASSED [ 75%] tests/test_cache.py::test_parse_cache_control[{'cache-control': ' , '}] PASSED [ 75%] tests/test_cache.py::test_get_cache_control_no_cache_no_store_request PASSED [ 75%] tests/test_cache.py::test_entry_disposition[({'cache-control': 'must-revalidate'}, {}, 'STALE')] PASSED [ 75%] tests/test_cache.py::test_entry_disposition[({}, {'cache-control': 'max-age=fred, min-fresh=barney'}, 'STALE')] PASSED [ 75%] tests/test_cache.py::test_update_invalidates_cache PASSED [ 76%] tests/test_cache.py::test_parse_cache_control[{'cache-control': 'Max-age=3600;post-check=1800,pre-check=3600'}] PASSED [ 76%] tests/test_cache.py::test_entry_disposition[({}, {'date': '{now}', 'cache-control': 'max-age=0'}, 'STALE')] PASSED [ 76%] tests/test_cache.py::test_entry_disposition[({}, {'data': '{now+3}'}, 'STALE')] PASSED [ 76%] tests/test_cache.py::test_get_cache_control_pragma_no_cache PASSED [ 76%] tests/test_cache.py::test_normalize_headers PASSED [ 77%] tests/test_cache.py::test_get_only_if_cached_cache_hit PASSED [ 77%] tests/test_cache.py::test_expiration_model_fresh PASSED [ 77%] tests/test_cache.py::test_vary_header_is_sent PASSED [ 77%] tests/test_cache.py::test_get_only_if_cached_cache_miss PASSED [ 77%] tests/test_cache.py::test_get_only_if_cached_no_cache_at_all PASSED [ 78%] tests/test_cache.py::test_entry_disposition[({'cache-control': 'max-age=0'}, {'date': '{now}', 'cache-control': 'max-age=2'}, 'STALE')] PASSED [ 78%] tests/test_cache.py::test_entry_disposition[({'cache-control': 'min-fresh=2'}, {'date': '{now}', 'expires': '{now+2}'}, 'STALE')] PASSED [ 78%] tests/test_cache.py::test_update_uses_cached_etag_overridden PASSED [ 78%] tests/test_cache.py::test_entry_disposition[({'cache-control': 'min-fresh=2'}, {'date': '{now}', 'expires': '{now+4}'}, 'FRESH')] PASSED [ 78%] tests/test_cache.py::test_entry_disposition[({'cache-control': 'only-if-cached'}, {}, 'FRESH')] PASSED [ 79%] tests/test_cache.py::test_get_cache_control_no_store_response PASSED [ 79%] tests/test_cache.py::test_vary_unused_header PASSED [ 79%] tests/test_cache.py::test_vary_header_double PASSED [ 79%] tests/test_cache.py::test_update_uses_cached_etag[PATCH] PASSED [ 80%] tests/test_cache.py::test_update_uses_cached_etag_and_oc_method PASSED [ 80%] tests/test_cache.py::test_parse_cache_control[{'cache-control': ' no-store, max-age = 7200'}] PASSED [ 80%] tests/test_cache.py::test_entry_disposition[({}, {'cache-control': 'must-revalidate'}, 'STALE')] PASSED [ 80%] tests/test_cache.py::test_parse_cache_control[{'cache-control': ' no-cache'}] PASSED [ 80%] tests/test_cache.py::test_entry_disposition[({}, {'date': '{now}', 'expires': '{now+3}', 'cache-control': 'no-cache'}, 'STALE')] PASSED [ 81%] tests/test_cache.py::test_entry_disposition[({}, {'date': '{now}', 'expires': '0'}, 'STALE')] PASSED [ 81%] tests/test_cache.py::test_entry_disposition[({}, {'date': '{now}', 'expires': '{now+3}'}, 'FRESH')] PASSED [ 81%] tests/test_cache.py::test_parse_cache_control[{}] PASSED [ 81%] tests/test_cache.py::test_get_cache_control_no_store_request PASSED [ 81%] tests/test_http.py::test_get_no_cache PASSED [ 82%] tests/test_http.py::test_bad_status_line_retry PASSED [ 82%] tests/test_http.py::test_get_302 PASSED [ 82%] tests/test_http.py::test_get_301_no_redirect XFAIL (FIXME: 301 cache...) [ 82%] tests/test_http.py::test_get_307 PASSED [ 82%] tests/test_http.py::test_get_302_no_location PASSED [ 83%] tests/test_http.py::test_custom_redirect_codes PASSED [ 83%] tests/test_http.py::test_etag_ignore PASSED [ 83%] tests/test_http.py::test_get_300_without_location PASSED [ 83%] tests/test_http.py::test_get_304_last_modified PASSED [ 83%] tests/test_http.py::test_inject_space PASSED [ 84%] tests/test_http.py::test_connection_refused_raises_exception PASSED [ 84%] tests/test_http.py::test_different_methods PASSED [ 84%] tests/test_http.py::test_cwe93_inject_crlf PASSED [ 84%] tests/test_http.py::test_head_read PASSED [ 84%] tests/test_http.py::test_change_308 PASSED [ 85%] tests/test_http.py::test_get_410 PASSED [ 85%] tests/test_http.py::test_get_iri PASSED [ 85%] tests/test_http.py::test_get_304_end_to_end SKIPPED (was commented i...) [ 85%] tests/test_http.py::test_connection_refused_returns_response PASSED [ 85%] tests/test_http.py::test_user_agent PASSED [ 86%] tests/test_http.py::test_get_301 PASSED [ 86%] tests/test_http.py::test_post_307 PASSED [ 86%] tests/test_http.py::test_get_302_redirection_limit PASSED [ 86%] tests/test_http.py::test_get_is_default_method PASSED [ 86%] tests/test_http.py::test_get_300_with_location PASSED [ 87%] tests/test_http.py::test_etag_override PASSED [ 87%] tests/test_http.py::test_get_duplicate_headers PASSED [ 87%] tests/test_http.py::test_user_agent_non_default PASSED [ 87%] tests/test_http.py::test_get_300_with_location_noredirect PASSED [ 87%] tests/test_http.py::test_unknown_server PASSED [ 88%] tests/test_http.py::test_etag_used PASSED [ 88%] tests/test_http.py::test_connection_type PASSED [ 88%] tests/test_https.py::test_set_tls_version[TLSv1_2-maximum_version] PASSED [ 88%] tests/test_https.py::test_http_redirect_https PASSED [ 88%] tests/test_https.py::test_get_301_via_https_spec_violation_on_location PASSED [ 89%] tests/test_https.py::test_invalid_ca_certs_path PASSED [ 89%] tests/test_https.py::test_not_trusted_ca PASSED [ 89%] tests/test_https.py::test_sni_set_servername_callback PASSED [ 89%] tests/test_https.py::test_client_cert_verified PASSED [ 90%] tests/test_https.py::test_set_tls_version[None-maximum_version] PASSED [ 90%] tests/test_https.py::test_set_tls_version[None-minimum_version] PASSED [ 90%] tests/test_https.py::test_max_tls_version PASSED [ 90%] tests/test_https.py::test_get_301_via_https PASSED [ 90%] tests/test_https.py::test_set_tls_version[TLSVersion.TLSv1_2-maximum_version] PASSED [ 91%] tests/test_https.py::test_https_redirect_http PASSED [ 91%] tests/test_https.py::test_set_tls_version[TLSVersion.TLSv1_2-minimum_version] PASSED [ 91%] tests/test_https.py::test_set_tls_version[TLSv1_2-minimum_version] PASSED [ 91%] tests/test_https.py::test_get_via_https PASSED [ 91%] tests/test_cacerts_from_env.py::test_certs_file_from_environment PASSED [ 92%] tests/test_cacerts_from_env.py::test_certs_file_from_builtin PASSED [ 92%] tests/test_cacerts_from_env.py::test_with_certifi_removed_from_modules PASSED [ 92%] tests/test_cacerts_from_env.py::test_certs_file_from_custom_getter PASSED [ 92%] tests/test_cacerts_from_env.py::test_certs_file_from_certifi PASSED [ 92%] tests/test_other.py::test_timeout_global XPASS (FIXME: for unknown r...) [ 93%] tests/test_other.py::test_pickle_custom_request_http PASSED [ 93%] tests/test_other.py::test_ipv6[https] PASSED [ 93%] tests/test_other.py::test_connect_exception_type PASSED [ 93%] tests/test_other.py::test_timeout_individual PASSED [ 93%] tests/test_other.py::test_reflect PASSED [ 94%] tests/test_other.py::test_convert_byte_str PASSED [ 94%] tests/test_other.py::test_pickle_http PASSED [ 94%] tests/test_other.py::test_close PASSED [ 94%] tests/test_other.py::test_connection_proxy_info_attribute_error[HTTPSConnectionWithTimeout] PASSED [ 94%] tests/test_other.py::test_connection_close PASSED [ 95%] tests/test_other.py::test_get_end2end_headers PASSED [ 95%] tests/test_other.py::test_ipv6[http] PASSED [ 95%] tests/test_other.py::test_pickle_http_with_connection PASSED [ 95%] tests/test_other.py::test_connection_proxy_info_attribute_error[HTTPConnectionWithTimeout] PASSED [ 95%] tests/test_other.py::test_timeout_https PASSED [ 96%] tests/test_other.py::test_timeout_subsequent PASSED [ 96%] tests/test_other.py::test_http_443_forced_https PASSED [ 96%] tests/test_uri.py::test_safename[('thisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuch', 'thisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuchthisistoomuc,c4553439dd179422c6acf6a8ac093eb6')] PASSED [ 96%] tests/test_uri.py::test_safename[('with/slash', 'withslash,17cc656656bb8ce2411bd41ead56d176')] PASSED [ 96%] tests/test_uri.py::test_safename[('foo://dom/path/brath/carapath', 'dompathbrathcarapath,83db942781ed975c7a5b7c24039f8ca3')] PASSED [ 97%] tests/test_uri.py::test_safename[(b'column\\tvalues/unstr.zip', 'columnvaluesunstr.zip,b9740dcd0553e11b526450ceb8f76683')] PASSED [ 97%] tests/test_uri.py::test_safename[('', ',d41d8cd98f00b204e9800998ecf8427e')] PASSED [ 97%] tests/test_uri.py::test_safename[('http://www/', 'www,1c73b6efd55cef1164fc084ecc331965')] PASSED [ 97%] tests/test_uri.py::test_safename[(b'\\xd0\\xbf\\xd1\\x80', ',9f18c0db74a9734e9d18461e16345083')] PASSED [ 97%] tests/test_uri.py::test_safename[('normal-resource-name.js', 'normal-resource-name.js,8ff7c46fd6e61bf4e91a0a1606954a54')] PASSED [ 98%] tests/test_uri.py::test_safename[('https://www.example.org/fred?/a=b', 'www.example.orgfreda=b,692e843a333484ce0095b070497ab45d')] PASSED [ 98%] tests/test_uri.py::test_safename[('\u043f\u0440', ',9f18c0db74a9734e9d18461e16345083')] PASSED [ 98%] tests/test_uri.py::test_safename[('http://\u2304.org/fred/?a=b', '.orgfreda=b,ecaf0f97756c0716de76f593bd60a35e')] PASSED [ 98%] tests/test_uri.py::test_norm PASSED [ 98%] tests/test_uri.py::test_safename[('http://www.example.org/fred?/a=b', 'www.example.orgfreda=b,499c44b8d844a011b67ea2c015116968')] PASSED [ 99%] tests/test_uri.py::test_from_std66 PASSED [ 99%] tests/test_uri.py::test_safename[('http://example.org/fred/?a=b', 'example.orgfreda=b,58489f63a7a83c3b7794a6a398ee8b1f')] PASSED [ 99%] tests/test_uri.py::test_safename[('http://example.org/fred?/a=b', 'example.orgfreda=b,8c5946d56fec453071f43329ff0be46b')] PASSED [ 99%] tests/test_uri.py::test_safename2 PASSED [100%] =============================== warnings summary =============================== tests/__init__.py:771 tests/__init__.py:771 tests/__init__.py:771 /build/source/tests/__init__.py:771: DeprecationWarning: ssl.SSLContext() without protocol argument is deprecated. return ssl.SSLContext() tests/__init__.py:771 tests/__init__.py:771 tests/__init__.py:771 /build/source/tests/__init__.py:771: DeprecationWarning: ssl.PROTOCOL_TLS is deprecated return ssl.SSLContext() -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html =========================== short test summary info ============================ SKIPPED [4] tests/test_auth.py:249: benchmark disabled by default, set env httplib2_test_bench=1 SKIPPED [1] tests/test_cache.py:48: was commented in legacy code SKIPPED [1] tests/test_http.py:525: was commented in legacy code XFAIL tests/test_http.py::test_get_301_no_redirect - FIXME: 301 cache works only with follow_redirects, should work regardless XPASS tests/test_other.py::test_timeout_global FIXME: for unknown reason global timeout test fails in Python3 with response 200 = 482 passed, 6 skipped, 3 deselected, 1 xfailed, 1 xpassed, 6 warnings in 12.56s = Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/q357fi619w1nxrlziij8ns16bniywfw6-python3.10-lazr.restfulclient-0.14.5.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh unpacking sources unpacking source archive /nix/store/1a71q3af8kpvxh7lwnm2jxllh73hsiiz-lazr.restfulclient-0.14.5.tar.gz source root is lazr.restfulclient-0.14.5 setting SOURCE_DATE_EPOCH to timestamp 1665841876 of file lazr.restfulclient-0.14.5/setup.cfg patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/dist.py:945: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. !! ******************************************************************************** Please replace its usage with implicit namespaces (PEP 420). See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. ******************************************************************************** !! ep.load()(self, ep.name, value) running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/lazr copying src/lazr/__init__.py -> build/lib/lazr creating build/lib/lazr/restfulclient copying src/lazr/restfulclient/_browser.py -> build/lib/lazr/restfulclient copying src/lazr/restfulclient/_json.py -> build/lib/lazr/restfulclient copying src/lazr/restfulclient/errors.py -> build/lib/lazr/restfulclient copying src/lazr/restfulclient/resource.py -> build/lib/lazr/restfulclient copying src/lazr/restfulclient/__init__.py -> build/lib/lazr/restfulclient creating build/lib/lazr/restfulclient/authorize copying src/lazr/restfulclient/authorize/oauth.py -> build/lib/lazr/restfulclient/authorize copying src/lazr/restfulclient/authorize/__init__.py -> build/lib/lazr/restfulclient/authorize creating build/lib/lazr/restfulclient/tests copying src/lazr/restfulclient/tests/test_oauth.py -> build/lib/lazr/restfulclient/tests copying src/lazr/restfulclient/tests/test_error.py -> build/lib/lazr/restfulclient/tests copying src/lazr/restfulclient/tests/test_docs.py -> build/lib/lazr/restfulclient/tests copying src/lazr/restfulclient/tests/__init__.py -> build/lib/lazr/restfulclient/tests copying src/lazr/restfulclient/tests/example.py -> build/lib/lazr/restfulclient/tests copying src/lazr/restfulclient/tests/test_atomicfilecache.py -> build/lib/lazr/restfulclient/tests running egg_info writing src/lazr.restfulclient.egg-info/PKG-INFO writing dependency_links to src/lazr.restfulclient.egg-info/dependency_links.txt writing namespace_packages to src/lazr.restfulclient.egg-info/namespace_packages.txt writing requirements to src/lazr.restfulclient.egg-info/requires.txt writing top-level names to src/lazr.restfulclient.egg-info/top_level.txt reading manifest file 'src/lazr.restfulclient.egg-info/SOURCES.txt' adding license file 'COPYING.txt' writing manifest file 'src/lazr.restfulclient.egg-info/SOURCES.txt' /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'lazr.restfulclient.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'lazr.restfulclient.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'lazr.restfulclient.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'lazr.restfulclient.docs' to be distributed and are already explicitly excluding 'lazr.restfulclient.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/CONTRIBUTING.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/Makefile -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/NEWS.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/authorizer.standalone.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/caching.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/collections.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/entries.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/hosted-files.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/index.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/operations.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/retry.standalone.rst -> build/lib/lazr/restfulclient/docs copying src/lazr/restfulclient/docs/toplevel.rst -> build/lib/lazr/restfulclient/docs /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib Skipping installation of build/bdist.linux-x86_64/wheel/lazr/__init__.py (namespace package) copying lazr/restfulclient/errors.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient copying lazr/restfulclient/resource.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient copying lazr/restfulclient/__init__.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient copying lazr/restfulclient/_json.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient copying lazr/restfulclient/_browser.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient copying lazr/restfulclient/authorize/oauth.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/authorize copying lazr/restfulclient/authorize/__init__.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/authorize copying lazr/restfulclient/docs/toplevel.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/CONTRIBUTING.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/operations.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/hosted-files.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/caching.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/retry.standalone.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/entries.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/authorizer.standalone.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/NEWS.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/collections.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/index.rst -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/docs/Makefile -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/docs copying lazr/restfulclient/tests/test_error.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/tests copying lazr/restfulclient/tests/test_atomicfilecache.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/tests copying lazr/restfulclient/tests/example.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/tests copying lazr/restfulclient/tests/test_oauth.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/tests copying lazr/restfulclient/tests/__init__.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/tests copying lazr/restfulclient/tests/test_docs.py -> build/bdist.linux-x86_64/wheel/lazr/restfulclient/tests running install_egg_info Copying src/lazr.restfulclient.egg-info to build/bdist.linux-x86_64/wheel/lazr.restfulclient-0.14.5-py3.10.egg-info Installing build/bdist.linux-x86_64/wheel/lazr.restfulclient-0.14.5-py3.10-nspkg.pth running install_scripts creating build/bdist.linux-x86_64/wheel/lazr.restfulclient-0.14.5.dist-info/WHEEL creating 'dist/lazr.restfulclient-0.14.5-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'lazr.restfulclient-0.14.5-py3.10-nspkg.pth' adding 'lazr/restfulclient/__init__.py' adding 'lazr/restfulclient/_browser.py' adding 'lazr/restfulclient/_json.py' adding 'lazr/restfulclient/errors.py' adding 'lazr/restfulclient/resource.py' adding 'lazr/restfulclient/authorize/__init__.py' adding 'lazr/restfulclient/authorize/oauth.py' adding 'lazr/restfulclient/docs/CONTRIBUTING.rst' adding 'lazr/restfulclient/docs/Makefile' adding 'lazr/restfulclient/docs/NEWS.rst' adding 'lazr/restfulclient/docs/authorizer.standalone.rst' adding 'lazr/restfulclient/docs/caching.rst' adding 'lazr/restfulclient/docs/collections.rst' adding 'lazr/restfulclient/docs/entries.rst' adding 'lazr/restfulclient/docs/hosted-files.rst' adding 'lazr/restfulclient/docs/index.rst' adding 'lazr/restfulclient/docs/operations.rst' adding 'lazr/restfulclient/docs/retry.standalone.rst' adding 'lazr/restfulclient/docs/toplevel.rst' adding 'lazr/restfulclient/tests/__init__.py' adding 'lazr/restfulclient/tests/example.py' adding 'lazr/restfulclient/tests/test_atomicfilecache.py' adding 'lazr/restfulclient/tests/test_docs.py' adding 'lazr/restfulclient/tests/test_error.py' adding 'lazr/restfulclient/tests/test_oauth.py' adding 'lazr.restfulclient-0.14.5.dist-info/COPYING.txt' adding 'lazr.restfulclient-0.14.5.dist-info/METADATA' adding 'lazr.restfulclient-0.14.5.dist-info/WHEEL' adding 'lazr.restfulclient-0.14.5.dist-info/namespace_packages.txt' adding 'lazr.restfulclient-0.14.5.dist-info/top_level.txt' adding 'lazr.restfulclient-0.14.5.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed lazr.restfulclient-0.14.5-py2.py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/jkr5mzy7x46kllc0m93nyl4rlp2szqcd-python3.10-lazr.restfulclient-0.14.5 checking for references to /build/ in /nix/store/jkr5mzy7x46kllc0m93nyl4rlp2szqcd-python3.10-lazr.restfulclient-0.14.5... patching script interpreter paths in /nix/store/jkr5mzy7x46kllc0m93nyl4rlp2szqcd-python3.10-lazr.restfulclient-0.14.5 stripping (with command strip and flags -S -p) in /nix/store/jkr5mzy7x46kllc0m93nyl4rlp2szqcd-python3.10-lazr.restfulclient-0.14.5/lib shrinking RPATHs of ELF executables and libraries in /nix/store/i625gs5swczw5l0xf6cl5shx6g7q3qvl-python3.10-lazr.restfulclient-0.14.5-dist checking for references to /build/ in /nix/store/i625gs5swczw5l0xf6cl5shx6g7q3qvl-python3.10-lazr.restfulclient-0.14.5-dist... patching script interpreter paths in /nix/store/i625gs5swczw5l0xf6cl5shx6g7q3qvl-python3.10-lazr.restfulclient-0.14.5-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: lazr.restfulclient building '/nix/store/vnnxj0jhdbx0f891lmd181clq6ypph1y-python3.10-launchpadlib-1.11.0.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing pytest-check-hook Using pytestCheckPhase unpacking sources unpacking source archive /nix/store/w775mvfwq5wz09a9a525q62mwb9plak3-launchpadlib-1.11.0.tar.gz source root is launchpadlib-1.11.0 setting SOURCE_DATE_EPOCH to timestamp 1673257952 of file launchpadlib-1.11.0/setup.cfg patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing pypaBuildPhase Creating a wheel... * Getting build dependencies for wheel... running egg_info writing src/launchpadlib.egg-info/PKG-INFO writing dependency_links to src/launchpadlib.egg-info/dependency_links.txt writing requirements to src/launchpadlib.egg-info/requires.txt writing top-level names to src/launchpadlib.egg-info/top_level.txt reading manifest file 'src/launchpadlib.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching '.gitignore' warning: no files found matching '*.xsl' anywhere in distribution no previously-included directories found matching 'src/launchpadlib/docs/_build' no previously-included directories found matching '.tox' adding license file 'COPYING.txt' writing manifest file 'src/launchpadlib.egg-info/SOURCES.txt' * Building wheel... running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/launchpadlib copying src/launchpadlib/apps.py -> build/lib/launchpadlib copying src/launchpadlib/uris.py -> build/lib/launchpadlib copying src/launchpadlib/credentials.py -> build/lib/launchpadlib copying src/launchpadlib/__init__.py -> build/lib/launchpadlib copying src/launchpadlib/errors.py -> build/lib/launchpadlib copying src/launchpadlib/launchpad.py -> build/lib/launchpadlib creating build/lib/launchpadlib/testing copying src/launchpadlib/testing/__init__.py -> build/lib/launchpadlib/testing copying src/launchpadlib/testing/resources.py -> build/lib/launchpadlib/testing copying src/launchpadlib/testing/launchpad.py -> build/lib/launchpadlib/testing copying src/launchpadlib/testing/helpers.py -> build/lib/launchpadlib/testing creating build/lib/launchpadlib/tests copying src/launchpadlib/tests/test_credential_store.py -> build/lib/launchpadlib/tests copying src/launchpadlib/tests/test_launchpad.py -> build/lib/launchpadlib/tests copying src/launchpadlib/tests/test_http.py -> build/lib/launchpadlib/tests copying src/launchpadlib/tests/__init__.py -> build/lib/launchpadlib/tests creating build/lib/launchpadlib/testing/tests copying src/launchpadlib/testing/tests/test_launchpad.py -> build/lib/launchpadlib/testing/tests copying src/launchpadlib/testing/tests/__init__.py -> build/lib/launchpadlib/testing/tests running egg_info writing src/launchpadlib.egg-info/PKG-INFO writing dependency_links to src/launchpadlib.egg-info/dependency_links.txt writing requirements to src/launchpadlib.egg-info/requires.txt writing top-level names to src/launchpadlib.egg-info/top_level.txt reading manifest file 'src/launchpadlib.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching '.gitignore' warning: no files found matching '*.xsl' anywhere in distribution no previously-included directories found matching 'src/launchpadlib/docs/_build' no previously-included directories found matching '.tox' adding license file 'COPYING.txt' writing manifest file 'src/launchpadlib.egg-info/SOURCES.txt' /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'launchpadlib.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'launchpadlib.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'launchpadlib.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'launchpadlib.docs' to be distributed and are already explicitly excluding 'launchpadlib.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'launchpadlib.docs.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'launchpadlib.docs.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'launchpadlib.docs.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'launchpadlib.docs.files' to be distributed and are already explicitly excluding 'launchpadlib.docs.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/launchpadlib/docs copying src/launchpadlib/docs/CONTRIBUTING.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/Makefile -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/NEWS.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/command-line.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/conf.py -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/hosted-files.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/index.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/introduction.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/operations.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/people.rst -> build/lib/launchpadlib/docs copying src/launchpadlib/docs/toplevel.rst -> build/lib/launchpadlib/docs creating build/lib/launchpadlib/docs/files copying src/launchpadlib/docs/files/mugshot.png -> build/lib/launchpadlib/docs/files copying src/launchpadlib/testing/launchpad-wadl.xml -> build/lib/launchpadlib/testing copying src/launchpadlib/testing/testing-wadl.xml -> build/lib/launchpadlib/testing installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/launchpadlib creating build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/operations.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/NEWS.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/command-line.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/introduction.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/Makefile -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/people.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/conf.py -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/CONTRIBUTING.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/hosted-files.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs creating build/bdist.linux-x86_64/wheel/launchpadlib/docs/files copying build/lib/launchpadlib/docs/files/mugshot.png -> build/bdist.linux-x86_64/wheel/launchpadlib/docs/files copying build/lib/launchpadlib/docs/toplevel.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/docs/index.rst -> build/bdist.linux-x86_64/wheel/launchpadlib/docs copying build/lib/launchpadlib/errors.py -> build/bdist.linux-x86_64/wheel/launchpadlib copying build/lib/launchpadlib/credentials.py -> build/bdist.linux-x86_64/wheel/launchpadlib copying build/lib/launchpadlib/launchpad.py -> build/bdist.linux-x86_64/wheel/launchpadlib creating build/bdist.linux-x86_64/wheel/launchpadlib/testing copying build/lib/launchpadlib/testing/__init__.py -> build/bdist.linux-x86_64/wheel/launchpadlib/testing creating build/bdist.linux-x86_64/wheel/launchpadlib/testing/tests copying build/lib/launchpadlib/testing/tests/test_launchpad.py -> build/bdist.linux-x86_64/wheel/launchpadlib/testing/tests copying build/lib/launchpadlib/testing/tests/__init__.py -> build/bdist.linux-x86_64/wheel/launchpadlib/testing/tests copying build/lib/launchpadlib/testing/launchpad.py -> build/bdist.linux-x86_64/wheel/launchpadlib/testing copying build/lib/launchpadlib/testing/launchpad-wadl.xml -> build/bdist.linux-x86_64/wheel/launchpadlib/testing copying build/lib/launchpadlib/testing/testing-wadl.xml -> build/bdist.linux-x86_64/wheel/launchpadlib/testing copying build/lib/launchpadlib/testing/resources.py -> build/bdist.linux-x86_64/wheel/launchpadlib/testing copying build/lib/launchpadlib/testing/helpers.py -> build/bdist.linux-x86_64/wheel/launchpadlib/testing copying build/lib/launchpadlib/apps.py -> build/bdist.linux-x86_64/wheel/launchpadlib creating build/bdist.linux-x86_64/wheel/launchpadlib/tests copying build/lib/launchpadlib/tests/test_credential_store.py -> build/bdist.linux-x86_64/wheel/launchpadlib/tests copying build/lib/launchpadlib/tests/test_http.py -> build/bdist.linux-x86_64/wheel/launchpadlib/tests copying build/lib/launchpadlib/tests/__init__.py -> build/bdist.linux-x86_64/wheel/launchpadlib/tests copying build/lib/launchpadlib/tests/test_launchpad.py -> build/bdist.linux-x86_64/wheel/launchpadlib/tests copying build/lib/launchpadlib/__init__.py -> build/bdist.linux-x86_64/wheel/launchpadlib copying build/lib/launchpadlib/uris.py -> build/bdist.linux-x86_64/wheel/launchpadlib running install_egg_info Copying src/launchpadlib.egg-info to build/bdist.linux-x86_64/wheel/launchpadlib-1.11.0-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/launchpadlib-1.11.0.dist-info/WHEEL creating '/build/launchpadlib-1.11.0/dist/.tmp-ms7twirz/launchpadlib-1.11.0-py2.py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'launchpadlib/__init__.py' adding 'launchpadlib/apps.py' adding 'launchpadlib/credentials.py' adding 'launchpadlib/errors.py' adding 'launchpadlib/launchpad.py' adding 'launchpadlib/uris.py' adding 'launchpadlib/docs/CONTRIBUTING.rst' adding 'launchpadlib/docs/Makefile' adding 'launchpadlib/docs/NEWS.rst' adding 'launchpadlib/docs/command-line.rst' adding 'launchpadlib/docs/conf.py' adding 'launchpadlib/docs/hosted-files.rst' adding 'launchpadlib/docs/index.rst' adding 'launchpadlib/docs/introduction.rst' adding 'launchpadlib/docs/operations.rst' adding 'launchpadlib/docs/people.rst' adding 'launchpadlib/docs/toplevel.rst' adding 'launchpadlib/docs/files/mugshot.png' adding 'launchpadlib/testing/__init__.py' adding 'launchpadlib/testing/helpers.py' adding 'launchpadlib/testing/launchpad-wadl.xml' adding 'launchpadlib/testing/launchpad.py' adding 'launchpadlib/testing/resources.py' adding 'launchpadlib/testing/testing-wadl.xml' adding 'launchpadlib/testing/tests/__init__.py' adding 'launchpadlib/testing/tests/test_launchpad.py' adding 'launchpadlib/tests/__init__.py' adding 'launchpadlib/tests/test_credential_store.py' adding 'launchpadlib/tests/test_http.py' adding 'launchpadlib/tests/test_launchpad.py' adding 'launchpadlib-1.11.0.dist-info/COPYING.txt' adding 'launchpadlib-1.11.0.dist-info/METADATA' adding 'launchpadlib-1.11.0.dist-info/WHEEL' adding 'launchpadlib-1.11.0.dist-info/top_level.txt' adding 'launchpadlib-1.11.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Successfully built launchpadlib-1.11.0-py2.py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase installing Executing pypaInstallPhase Successfully installed launchpadlib-1.11.0-py2.py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/rmka5raa2k739g6ac9fb0ynpdll8qnsq-python3.10-launchpadlib-1.11.0 checking for references to /build/ in /nix/store/rmka5raa2k739g6ac9fb0ynpdll8qnsq-python3.10-launchpadlib-1.11.0... patching script interpreter paths in /nix/store/rmka5raa2k739g6ac9fb0ynpdll8qnsq-python3.10-launchpadlib-1.11.0 stripping (with command strip and flags -S -p) in /nix/store/rmka5raa2k739g6ac9fb0ynpdll8qnsq-python3.10-launchpadlib-1.11.0/lib shrinking RPATHs of ELF executables and libraries in /nix/store/gv5qga6ir046idxbmfj121zy19hny782-python3.10-launchpadlib-1.11.0-dist checking for references to /build/ in /nix/store/gv5qga6ir046idxbmfj121zy19hny782-python3.10-launchpadlib-1.11.0-dist... patching script interpreter paths in /nix/store/gv5qga6ir046idxbmfj121zy19hny782-python3.10-launchpadlib-1.11.0-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir running install tests no Makefile or custom installCheckPhase, doing nothing pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: launchpadlib launchpadlib.apps launchpadlib.credentials pytestCheckPhase Executing pytestCheckPhase ============================= test session starts ============================== platform linux -- Python 3.10.12, pytest-7.4.0, pluggy-1.2.0 rootdir: /build/launchpadlib-1.11.0 collected 115 items src/launchpadlib/testing/tests/test_launchpad.py ....................... [ 20%] ........................ [ 40%] src/launchpadlib/tests/test_credential_store.py ............ [ 51%] src/launchpadlib/tests/test_http.py .......... [ 60%] src/launchpadlib/tests/test_launchpad.py ............................... [ 86%] ............... [100%] =============================== warnings summary =============================== src/launchpadlib/testing/resources.py:21 /build/launchpadlib-1.11.0/src/launchpadlib/testing/resources.py:21: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html from pkg_resources import resource_string -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ======================== 115 passed, 1 warning in 0.64s ======================== Finished executing pytestCheckPhase pytestcachePhase pytestRemoveBytecodePhase building '/nix/store/rv60cgr1fn5ykkrjqf06mbs7078wcbzr-python3.10-breezy-3.3.4.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh unpacking sources unpacking source archive /nix/store/v096j65yf3f45hxiwgf9xzy31vlfp5sp-breezy-3.3.4.tar.gz source root is breezy-3.3.4 Executing cargoSetupPostUnpackHook Finished cargoSetupPostUnpackHook setting SOURCE_DATE_EPOCH to timestamp 1693847390 of file breezy-3.3.4/setup.cfg patching sources Executing cargoSetupPostPatchHook Validating consistency between /build/breezy-3.3.4/Cargo.lock and /build/cargo-vendor-dir/Cargo.lock Finished cargoSetupPostPatchHook updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing pypaBuildPhase Creating a wheel... * Getting build dependencies for wheel... :106: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. :107: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) running egg_info writing breezy.egg-info/PKG-INFO writing dependency_links to breezy.egg-info/dependency_links.txt writing requirements to breezy.egg-info/requires.txt writing top-level names to breezy.egg-info/top_level.txt /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/sdist.py:121: SetuptoolsDeprecationWarning: Direct usage of `distutils` commands !! ******************************************************************************** It seems that you are using `distutils.command.build` to add new subcommands. Using `distutils` directly is considered deprecated, please use `setuptools.command.build`. By 2023-Dec-13, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://peps.python.org/pep-0632/ for details. ******************************************************************************** !! missing_cmds = set(build.get_sub_commands()) - _ORIGINAL_SUBCOMMANDS reading manifest file 'breezy.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING.txt' writing manifest file 'breezy.egg-info/SOURCES.txt' * Building wheel... :106: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. :107: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. config = read_configuration(filepath, True, ignore_option_errors, dist) running bdist_wheel running build /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/command/build.py:130: SetuptoolsDeprecationWarning: Direct usage of `distutils` commands !! ******************************************************************************** It seems that you are using `distutils.command.build` to add new subcommands. Using `distutils` directly is considered deprecated, please use `setuptools.command.build`. By 2023-Dec-13, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://peps.python.org/pep-0632/ for details. ******************************************************************************** !! for cmd_name in self.get_sub_commands(): running build_py creating build creating build/lib.linux-x86_64-cpython-310 creating build/lib.linux-x86_64-cpython-310/breezy copying breezy/location.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/check.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/lazy_import.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/grep.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/reconfigure.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/gpg.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/tag.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/_chunks_to_lines_py.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/revisionspec.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/estimate_compressed_size.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/mail_client.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/cmdline.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/multiwalker.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/breakin.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/timestamp.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/cethread.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/lock.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/atomicfile.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/info.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/textmerge.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/textfile.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/email_message.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/fetch_ghosts.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/_termcolor.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/dirty_tracker.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/export.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/debug.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/cmd_version_info.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/registry.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/progress.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/lazy_regex.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/urlutils.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/strace.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/upstream_import.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/decorators.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/multiparent.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/version.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/repository.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/pyutils.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/annotate.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/mergeable.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/bisect_multi.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/directory_service.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/diff.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/status.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/transactions.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/_annotator_py.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/graph.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/fifo_cache.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/filter_tree.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/switch.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/symbol_versioning.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/memorybranch.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/_known_graph_py.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/revisiontree.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/rules.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/bzr_distutils.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/revision.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/send.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/smtp_connection.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/merge.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/config.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/log.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/shelf.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/lsprof.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/help.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/library_state.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/tsort.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/controldir.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/upgrade.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/iterablefile.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/export_pot.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/push.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/colordiff.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/uncommit.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/option.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/commands.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/hooks.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/patches.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/lockable_files.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/i18n.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/workspace.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/globbing.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/cache_utf8.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/missing.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/inter.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/branch.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/delta.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/identitymap.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/transform.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/add.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/__main__.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/counted_lock.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/bugtracker.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/commit_signature_commands.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/externalcommand.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/branchbuilder.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/cmd_test_script.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/msgeditor.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/rename_map.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/lru_cache.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/crash.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/memorytree.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/osutils.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/foreign.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/bedding.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/plugin.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/mergetools.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/terminal.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/merge_directive.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/ignores.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/forge.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/tree.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/win32utils.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/mutabletree.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/bisect.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/patch.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/shelf_ui.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/shellcomplete.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/treebuilder.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/errors.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/utextwrap.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/views.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/url_policy_open.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/lockdir.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/chunk_writer.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/builtins.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/trace.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/conflicts.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/commit.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/_readdir_py.py -> build/lib.linux-x86_64-cpython-310/breezy copying breezy/clean_tree.py -> build/lib.linux-x86_64-cpython-310/breezy creating build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/static_tuple.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/transform.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/_btree_serializer_py.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/_groupcompress_py.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/generate_ids.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/xml5.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/_rio_py.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/xml7.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/dirstate.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/branch.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/xml6.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/inventory_delta.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/tag.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/chk_serializer.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/conflicts.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/inventory.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/knit.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/_dirstate_helpers_py.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/rio.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/_static_tuple_py.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/weavefile.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/remote.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/xml_serializer.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/check.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/knitrepo.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/groupcompress.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/vf_search.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/workingtree_4.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/xml8.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/debug_commands.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/recordcounter.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/hashcache.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/serializer.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/groupcompress_repo.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/index.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/pack.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/pack_repo.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/repository.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/testament.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/fullhistory.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/workingtree_3.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/bzrdir.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/_knit_load_data_py.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/_chk_map_py.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/vf_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/tuned_gzip.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/inventorytree.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/versionedfile.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/weave.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/btree_index.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/knitpack_repo.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/chk_map.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr copying breezy/bzr/textinv.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr creating build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_lsprof.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/stub_sftp.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/features.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/matchers.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_http_response.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_filter_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_config.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_selftest.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_delta.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_cache_utf8.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_ancestry.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/file_utils.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_filters.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/transport_util.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_switch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_chunk_writer.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_bugtracker.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_eol_filters.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_status.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test__annotator.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_revert.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_ssh_transport.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_script.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_i18n.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_tag.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_gpg.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_export_pot.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_textmerge.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/fake_command.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_import_tariff.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_shelf_ui.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_timestamp.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_controldir.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_https_urllib.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_tsort.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_dirty_tracker.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/testui.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_strace.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/ui_testing.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_matchers.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_hooks.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_multiparent.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_features.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_treeshape.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_transport_log.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_scenarios.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_help.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test__known_graph.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_cmdline.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_export.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_patch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_version.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_email_message.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_pyutils.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_wsgi.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_lockable_files.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_transport.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_multiwalker.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/per_merger.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test__walkdirs_win32.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_mail_client.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_win32utils.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_ui.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_mergeable.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_trace.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_clean_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_sftp_transport.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_merge_directive.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_bad_files.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_log.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_views.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_uncommit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_test_server.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_commands.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_symbol_versioning.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_counted_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_setup.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_sampler.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_crash.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_reconfigure.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_globbing.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_plugins.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_generate_docs.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_lazy_import.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_commit_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_memorytree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_rename_map.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_directory_service.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_url_policy_open.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_options.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/http_server.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_subsume.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_forge.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_merge_core.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_mergetools.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_registry.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_commit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_progress.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_treebuilder.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_memorybranch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_urlutils.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_info.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_mutabletree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_transactions.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_patches.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_workspace.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_upgrade_stacked.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/per_transport.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_upgrade.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_errors.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_annotate.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_bisect.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_revisiontree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/fixtures.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_atomicfile.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test__chunks_to_lines.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_transform.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_smart_add.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/EncodingAdapter.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_fixtures.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/script.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/https_server.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_nonascii.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_bisect_multi.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_version_info.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_missing.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_grep.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_revision.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_extract.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_fifo_cache.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_location.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_ignores.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_branchbuilder.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_graph.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_fetch_ghosts.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_rules.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_upstream_import.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_https_ca_bundle.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_msgeditor.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_bedding.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_lru_cache.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_branch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/TestUtil.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_shelf.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_osutils.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_foreign.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_permissions.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_identitymap.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_diff.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/scenarios.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_lazy_regex.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_source.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/lock_helpers.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_estimate_compressed_size.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_server.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_debug.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_utextwrap.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_whitebox.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_conflicts.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/treeshape.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_lockdir.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_library_state.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_http.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_osutils_encodings.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_cethread.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/http_utils.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_revisionspec.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_smtp_connection.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_decorators.py -> build/lib.linux-x86_64-cpython-310/breezy/tests copying breezy/tests/test_textfile.py -> build/lib.linux-x86_64-cpython-310/breezy/tests creating build/lib.linux-x86_64-cpython-310/breezy/doc_generate copying breezy/doc_generate/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/doc_generate copying breezy/doc_generate/autodoc_bash_completion.py -> build/lib.linux-x86_64-cpython-310/breezy/doc_generate copying breezy/doc_generate/autodoc_man.py -> build/lib.linux-x86_64-cpython-310/breezy/doc_generate copying breezy/doc_generate/conf.py -> build/lib.linux-x86_64-cpython-310/breezy/doc_generate copying breezy/doc_generate/autodoc_rstx.py -> build/lib.linux-x86_64-cpython-310/breezy/doc_generate creating build/lib.linux-x86_64-cpython-310/breezy/archive copying breezy/archive/zip.py -> build/lib.linux-x86_64-cpython-310/breezy/archive copying breezy/archive/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/archive copying breezy/archive/tar.py -> build/lib.linux-x86_64-cpython-310/breezy/archive creating build/lib.linux-x86_64-cpython-310/breezy/filters copying breezy/filters/eol.py -> build/lib.linux-x86_64-cpython-310/breezy/filters copying breezy/filters/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/filters creating build/lib.linux-x86_64-cpython-310/breezy/version_info_formats copying breezy/version_info_formats/format_custom.py -> build/lib.linux-x86_64-cpython-310/breezy/version_info_formats copying breezy/version_info_formats/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/version_info_formats copying breezy/version_info_formats/format_rio.py -> build/lib.linux-x86_64-cpython-310/breezy/version_info_formats copying breezy/version_info_formats/format_yaml.py -> build/lib.linux-x86_64-cpython-310/breezy/version_info_formats copying breezy/version_info_formats/format_python.py -> build/lib.linux-x86_64-cpython-310/breezy/version_info_formats creating build/lib.linux-x86_64-cpython-310/breezy/ui copying breezy/ui/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/ui copying breezy/ui/text.py -> build/lib.linux-x86_64-cpython-310/breezy/ui creating build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/branch.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/pristine_tar.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/annotate.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/refs.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/git_remote_helper.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/filegraph.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/roundtrip.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/server.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/unpeel_map.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/cache.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/errors.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/remote.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/commit.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/repository.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/revspec.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/send.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/help.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/dir.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/interrepo.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/push.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/transform.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/transportgit.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/object_store.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/config.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/hg.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/tree.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/commands.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/mapping.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/directory.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/urls.py -> build/lib.linux-x86_64-cpython-310/breezy/git copying breezy/git/memorytree.py -> build/lib.linux-x86_64-cpython-310/breezy/git creating build/lib.linux-x86_64-cpython-310/breezy/util copying breezy/util/simplemapi.py -> build/lib.linux-x86_64-cpython-310/breezy/util copying breezy/util/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/util creating build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/chroot.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/nosmart.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/ssh.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/readonly.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/trace.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/local.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/sftp.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/fakevfat.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/unlistable.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/log.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/decorator.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/brokenrename.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/pathfilter.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/gio_transport.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/memory.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/fakenfs.py -> build/lib.linux-x86_64-cpython-310/breezy/transport copying breezy/transport/remote.py -> build/lib.linux-x86_64-cpython-310/breezy/transport creating build/lib.linux-x86_64-cpython-310/breezy/help_topics copying breezy/help_topics/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/help_topics creating build/lib.linux-x86_64-cpython-310/breezy/doc copying breezy/doc/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/doc creating build/lib.linux-x86_64-cpython-310/breezy/plugins copying breezy/plugins/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins creating build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle copying breezy/bzr/bundle/commands.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle copying breezy/bzr/bundle/apply_bundle.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle copying breezy/bzr/bundle/bundle_data.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle copying breezy/bzr/bundle/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle creating build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_inv.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_smart.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_bundle.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test__dirstate_helpers.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_tuned_gzip.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_tag.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_transform.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test__simple_set.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_bzrdir.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/matchers.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_versionedfile.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_index.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_knit.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_conflicts.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test__btree_serializer.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_chk_map.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_xml.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_read_bundle.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_vfs_ratchet.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_rio.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test__rio.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_groupcompress.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test__groupcompress.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_workingtree_4.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_serializer.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/per_pack_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_weave.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_btree_index.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_matchers.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_smart_signals.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_vf_search.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_chk_serializer.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_smart_transport.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test__static_tuple.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_generate_ids.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_inventory_delta.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_dirstate.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_hashcache.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_remote.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_testament.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_pack.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test_smart_request.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/test__chk_map.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests copying breezy/bzr/tests/per_versionedfile.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests creating build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/signals.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/request.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/bzrdir.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/client.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/branch.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/repository.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/protocol.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/packrepository.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/medium.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/server.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/message.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/ping.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart copying breezy/bzr/smart/vfs.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/smart creating build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer copying breezy/bzr/bundle/serializer/v09.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer copying breezy/bzr/bundle/serializer/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer copying breezy/bzr/bundle/serializer/v4.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer copying breezy/bzr/bundle/serializer/v08.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer creating build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_chk copying breezy/bzr/tests/per_repository_chk/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_chk copying breezy/bzr/tests/per_repository_chk/test_supported.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_chk copying breezy/bzr/tests/per_repository_chk/test_unsupported.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_chk creating build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_bzrdir copying breezy/bzr/tests/per_bzrdir/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_bzrdir copying breezy/bzr/tests/per_bzrdir/test_bzrdir.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_bzrdir creating build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_merge_directive.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/helpers.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_fileid_involved.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_check.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_add_inventory_by_delta.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_write_group.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_check_reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_find_text_key_references.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test__generate_text_key_index.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf copying breezy/bzr/tests/per_repository_vf/test_refresh_data.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf creating build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_inventory copying breezy/bzr/tests/per_inventory/basics.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_inventory copying breezy/bzr/tests/per_inventory/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_inventory creating build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/blackbox copying breezy/bzr/tests/blackbox/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/blackbox copying breezy/bzr/tests/blackbox/test_dump_btree.py -> build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/blackbox creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch copying breezy/tests/per_interbranch/test_copy_content_into.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch copying breezy/tests/per_interbranch/test_get.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch copying breezy/tests/per_interbranch/test_pull.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch copying breezy/tests/per_interbranch/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch copying breezy/tests/per_interbranch/test_fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch copying breezy/tests/per_interbranch/test_push.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch creating build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs copying breezy/tests/ssl_certs/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs copying breezy/tests/ssl_certs/create_ssls.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_sprout.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_break_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_iter_merge_sorted_revisions.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_check.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_permissions.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_config.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_parent.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_tags.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_push.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_get_rev_id.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_revision_id_to_revno.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_last_revision_info.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_revision_id_to_dotted_revno.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_locking.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_get_revision_id_to_revno_map.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_update.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_create_clone.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_hooks.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_stacking.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_commit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_pull.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_dotted_revno_to_revision_id.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_create_checkout.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_uncommit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_http.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch copying breezy/tests/per_branch/test_branch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch creating build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_init.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_commit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_checkout.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_branch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_push.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_init_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_revert.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_missing.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_cat.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_update.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands copying breezy/tests/commands/test_pull.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/commands creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_walkdirs.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_get_file_with_stat.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_annotate_iter.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_test_trees.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_iter_search_rules.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_export.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_transform.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_revision_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_list_files.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_is_executable.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_get_symlink_target.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_ids.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_locking.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_symlinks.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_get_file_mtime.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_get_root_id.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_archive.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree copying breezy/tests/per_tree/test_path_content_summary.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir_colo copying breezy/tests/per_controldir_colo/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir_colo copying breezy/tests/per_controldir_colo/test_unsupported.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir_colo copying breezy/tests/per_controldir_colo/test_supported.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir_colo creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_uifactory copying breezy/tests/per_uifactory/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_uifactory creating build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_locale.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_testament.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_serve.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_too_much.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_break_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_view.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_re_sign.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_info.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_remerge.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_unknowns.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_ls.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_modified.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_ping.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_bundle_info.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_filesystem_cicp.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_mv.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_bisect.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_commit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_patch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_ancestry.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_pull.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_split.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_selftest.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_exceptions.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_lookup_revision.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_hooks.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_outside_wt.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_alias.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_versioning.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_version.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_send.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_repair_workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_find_merge_base.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_join.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_branch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_log.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_cp.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_uncommit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_plugins.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_added.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_mkdir.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_diff.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_pack.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_remember_option.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_revision_info.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_reference.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_nick.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_merge_directive.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_export.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_remove.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_upgrade.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_ignore.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_deleted.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_cat.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_fetch_ghosts.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_big_file.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_debug.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_help.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_switch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_add.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_missing.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_annotate.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_branches.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_status.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_revert.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_script.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_revision_history.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_push.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_export_pot.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_config.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_import.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_lsprof.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_tags.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_checkout.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_reconfigure.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_init.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_clean_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_logformats.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_bound_branches.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_shelve.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_link_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_ignored.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_resolve_location.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_non_ascii.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_aliases.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_verify_signatures.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_resolve.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_filtered_view_ops.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_whoami.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_check.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_cat_revision.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_sign_my_commits.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_shared_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_remove_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_revno.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_conflicts.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_version_info.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_clone.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_rmbranch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_command_encoding.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_shell_complete.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_inventory.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox copying breezy/tests/blackbox/test_update.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_interrepository copying breezy/tests/per_interrepository/test_fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interrepository copying breezy/tests/per_interrepository/test_interrepository.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interrepository copying breezy/tests/per_interrepository/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_interrepository creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree copying breezy/tests/per_intertree/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree copying breezy/tests/per_intertree/test_file_content_matches.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree copying breezy/tests/per_intertree/test_find_path.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree copying breezy/tests/per_intertree/test_compare.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_lock copying breezy/tests/per_lock/test_temporary_write_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_lock copying breezy/tests/per_lock/test_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_lock copying breezy/tests/per_lock/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_lock creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir copying breezy/tests/per_controldir/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir copying breezy/tests/per_controldir/test_push.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir copying breezy/tests/per_controldir/test_format.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir copying breezy/tests/per_controldir/test_controldir.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_check.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_revision.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_add_fallback_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_commit_builder.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_has_same_location.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_statistics.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_get_rev_id_for_revno.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_file_graph.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_has_revisions.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_pack.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_locking.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_signatures.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_get_parent_map.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_write_group.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_reconcile.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_break_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository copying breezy/tests/per_repository/test_refresh_data.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_add_inventory.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_unlock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_initialize.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_commit_with_stacking.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_get_record_stream.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_get_rev_id_for_revno.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_add_signature_text.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_default_stacking.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test__make_parents_provider.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_break_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_check.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_add_revision.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_all_revision_ids.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference copying breezy/tests/per_repository_reference/test_graph.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_uncommit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_rename_one.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_walkdirs.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_inv.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_read_working_inventory.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_check.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_unversion.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_executable.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_content_filters.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_locking.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_move.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_set_root_id.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_revision_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_break_lock.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_changes_from.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_add_reference.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_put_file.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_basis_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_remove.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_basis_inventory.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_mkdir.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_shelf_manager.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_readonly.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_is_ignored.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_merge_from_branch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_paths2ids.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_transform.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_add.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_symlinks.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_smart_add.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_commit.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_is_control_filename.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_get_parent_ids.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_views.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_parents.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_flush.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_canonical_path.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_get_file_mtime.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_annotate_iter.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_nested_specifics.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_eol_conversion.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_check_state.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree copying breezy/tests/per_workingtree/test_pull.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree creating build/lib.linux-x86_64-cpython-310/breezy/tests/per_foreign_vcs copying breezy/tests/per_foreign_vcs/test_branch.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_foreign_vcs copying breezy/tests/per_foreign_vcs/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_foreign_vcs copying breezy/tests/per_foreign_vcs/test_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/tests/per_foreign_vcs creating build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_roundtrip.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_object_store.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_fetch.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_transportgit.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_remote.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_mapping.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_refs.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_server.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_unpeel_map.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_branch.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_builder.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_tree.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_git_remote_helper.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_memorytree.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_dir.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_urls.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_transform.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_pristine_tar.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_revspec.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_push.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_cache.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests copying breezy/git/tests/test_blackbox.py -> build/lib.linux-x86_64-cpython-310/breezy/git/tests creating build/lib.linux-x86_64-cpython-310/breezy/util/tests copying breezy/util/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/util/tests creating build/lib.linux-x86_64-cpython-310/breezy/transport/http copying breezy/transport/http/response.py -> build/lib.linux-x86_64-cpython-310/breezy/transport/http copying breezy/transport/http/ca_bundle.py -> build/lib.linux-x86_64-cpython-310/breezy/transport/http copying breezy/transport/http/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/transport/http copying breezy/transport/http/wsgi.py -> build/lib.linux-x86_64-cpython-310/breezy/transport/http copying breezy/transport/http/urllib.py -> build/lib.linux-x86_64-cpython-310/breezy/transport/http creating build/lib.linux-x86_64-cpython-310/breezy/doc/api copying breezy/doc/api/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/doc/api creating build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews copying breezy/plugins/commitfromnews/committemplate.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews copying breezy/plugins/commitfromnews/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews creating build/lib.linux-x86_64-cpython-310/breezy/plugins/upload copying breezy/plugins/upload/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/upload copying breezy/plugins/upload/cmds.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/upload creating build/lib.linux-x86_64-cpython-310/breezy/plugins/pypi copying breezy/plugins/pypi/directory.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/pypi copying breezy/plugins/pypi/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/pypi creating build/lib.linux-x86_64-cpython-310/breezy/plugins/hg copying breezy/plugins/hg/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/hg creating build/lib.linux-x86_64-cpython-310/breezy/plugins/cvs copying breezy/plugins/cvs/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/cvs creating build/lib.linux-x86_64-cpython-310/breezy/plugins/mtn copying breezy/plugins/mtn/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/mtn creating build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store copying breezy/plugins/netrc_credential_store/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store creating build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge copying breezy/plugins/news_merge/news_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge copying breezy/plugins/news_merge/parser.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge copying breezy/plugins/news_merge/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge creating build/lib.linux-x86_64-cpython-310/breezy/plugins/stats copying breezy/plugins/stats/classify.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/stats copying breezy/plugins/stats/test_blackbox.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/stats copying breezy/plugins/stats/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/stats copying breezy/plugins/stats/test_classify.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/stats copying breezy/plugins/stats/test_stats.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/stats copying breezy/plugins/stats/cmds.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/stats creating build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/lp_api.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/test_lp_directory.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/test_account.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/lp_directory.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/account.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/test_lp_api.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/cmds.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/uris.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/test_lp_login.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad copying breezy/plugins/launchpad/forge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad creating build/lib.linux-x86_64-cpython-310/breezy/plugins/darcs copying breezy/plugins/darcs/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/darcs creating build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion copying breezy/plugins/zsh_completion/zshcomp.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion copying breezy/plugins/zsh_completion/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion creating build/lib.linux-x86_64-cpython-310/breezy/plugins/github copying breezy/plugins/github/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/github copying breezy/plugins/github/cmds.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/github copying breezy/plugins/github/forge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/github creating build/lib.linux-x86_64-cpython-310/breezy/plugins/fossil copying breezy/plugins/fossil/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fossil creating build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab copying breezy/plugins/gitlab/forge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab copying breezy/plugins/gitlab/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab copying breezy/plugins/gitlab/cmds.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab creating build/lib.linux-x86_64-cpython-310/breezy/plugins/email copying breezy/plugins/email/emailer.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/email copying breezy/plugins/email/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/email creating build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite copying breezy/plugins/rewrite/pseudonyms.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite copying breezy/plugins/rewrite/upgrade.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite copying breezy/plugins/rewrite/maptree.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite copying breezy/plugins/rewrite/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite copying breezy/plugins/rewrite/rebase.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite copying breezy/plugins/rewrite/commands.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite creating build/lib.linux-x86_64-cpython-310/breezy/plugins/svn copying breezy/plugins/svn/revspec.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/svn copying breezy/plugins/svn/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/svn creating build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion copying breezy/plugins/bash_completion/bashcomp.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion copying breezy/plugins/bash_completion/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion creating build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/branch.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/xml4.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/test_bzrdir.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/test_workingtree.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/repository.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/test_repository.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/bzrdir.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt copying breezy/plugins/weave_fmt/test_store.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt creating build/lib.linux-x86_64-cpython-310/breezy/plugins/propose copying breezy/plugins/propose/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/propose copying breezy/plugins/propose/cmds.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/propose creating build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge copying breezy/plugins/po_merge/po_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge copying breezy/plugins/po_merge/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge creating build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/branch_mapper.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/bzr_commit_handler.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/cmds.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/idmapfile.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/marks_file.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/revision_store.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/cache_manager.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/user_mapper.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/helpers.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/branch_updater.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport copying breezy/plugins/fastimport/exporter.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport creating build/lib.linux-x86_64-cpython-310/breezy/plugins/flake8 copying breezy/plugins/flake8/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/flake8 creating build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge copying breezy/plugins/changelog_merge/changelog_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge copying breezy/plugins/changelog_merge/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge creating build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav copying breezy/plugins/webdav/webdav.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav copying breezy/plugins/webdav/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav creating build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/missing_keys_for_stacking_fixer.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/chk_used_by.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/repo_keys.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/fetch_all_records.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/file_refs.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/check_chk.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug copying breezy/plugins/repodebug/repo_has_key.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug creating build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt copying breezy/plugins/quilt/quilt.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt copying breezy/plugins/quilt/wrapper.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt copying breezy/plugins/quilt/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt copying breezy/plugins/quilt/merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt creating build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/tests copying breezy/plugins/commitfromnews/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/tests copying breezy/plugins/commitfromnews/tests/test_committemplate.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/tests copying breezy/plugins/commitfromnews/tests/test_msgeditor.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/tests copying breezy/plugins/upload/tests/test_auto_upload_hook.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/tests copying breezy/plugins/upload/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/tests copying breezy/plugins/upload/tests/test_upload.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store/tests copying breezy/plugins/netrc_credential_store/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store/tests copying breezy/plugins/netrc_credential_store/tests/test_netrc.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/tests copying breezy/plugins/news_merge/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/tests copying breezy/plugins/news_merge/tests/test_news_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion/tests copying breezy/plugins/zsh_completion/tests/test_zshcomp.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion/tests copying breezy/plugins/zsh_completion/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/github/tests copying breezy/plugins/github/tests/test_forge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/github/tests copying breezy/plugins/github/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/github/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/tests copying breezy/plugins/gitlab/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/tests copying breezy/plugins/gitlab/tests/test_forge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/email/tests copying breezy/plugins/email/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/email/tests copying breezy/plugins/email/tests/testemail.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/email/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests copying breezy/plugins/rewrite/tests/test_blackbox.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests copying breezy/plugins/rewrite/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests copying breezy/plugins/rewrite/tests/test_upgrade.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests copying breezy/plugins/rewrite/tests/test_rebase.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests copying breezy/plugins/rewrite/tests/test_pseudonyms.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests copying breezy/plugins/rewrite/tests/test_maptree.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion/tests copying breezy/plugins/bash_completion/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion/tests copying breezy/plugins/bash_completion/tests/test_bashcomp.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/store copying breezy/plugins/weave_fmt/store/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/store copying breezy/plugins/weave_fmt/store/versioned.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/store copying breezy/plugins/weave_fmt/store/text.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/store creating build/lib.linux-x86_64-cpython-310/breezy/plugins/propose/tests copying breezy/plugins/propose/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/propose/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge/tests copying breezy/plugins/po_merge/tests/test_po_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge/tests copying breezy/plugins/po_merge/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/test_generic_processor.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/test_marks_file.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/test_revision_store.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/test_exporter.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/test_commands.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/test_head_tracking.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests copying breezy/plugins/fastimport/tests/test_branch_mapper.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/processors copying breezy/plugins/fastimport/processors/generic_processor.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/processors copying breezy/plugins/fastimport/processors/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/processors creating build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge/tests copying breezy/plugins/changelog_merge/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge/tests copying breezy/plugins/changelog_merge/tests/test_changelog_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/tests copying breezy/plugins/webdav/tests/test_webdav.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/tests copying breezy/plugins/webdav/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/tests copying breezy/plugins/webdav/tests/dav_server.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/tests copying breezy/plugins/repodebug/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/tests creating build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/tests copying breezy/plugins/quilt/tests/test_merge.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/tests copying breezy/plugins/quilt/tests/test_wrapper.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/tests copying breezy/plugins/quilt/tests/__init__.py -> build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/tests copying breezy/doc/api/transport.txt -> build/lib.linux-x86_64-cpython-310/breezy/doc/api copying breezy/doc/api/branch.txt -> build/lib.linux-x86_64-cpython-310/breezy/doc/api creating build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/orig-7 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/insert_top.patch -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/mod -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/diff-7 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/mod-7 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/orig -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/patchtext.patch -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/orig-4 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/diff-4 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/mod-3 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/binary.patch -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/mod-4 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/diff-3 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/orig-3 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/diff -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/mod-6 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/diff-6 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/orig-6 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/binary-after-normal.patch -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/orig-2 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/mod-5 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/diff-2 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/diff-5 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/mod-2 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data copying breezy/tests/test_patches_data/orig-5 -> build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data creating build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/eol.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/glossary.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/patterns.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/configuration.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/missing-extensions.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/rules.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/content-filters.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/conflict-types.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/authentication.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/diverged-branches.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/log-formats.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/debug-flags.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/help_topics/en/url-special-chars.txt -> build/lib.linux-x86_64-cpython-310/breezy/help_topics/en copying breezy/tests/ssl_certs/ca.crt -> build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs copying breezy/tests/ssl_certs/server_without_pass.key -> build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs copying breezy/tests/ssl_certs/server_with_pass.key -> build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs copying breezy/tests/ssl_certs/server.crt -> build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs copying breezy/py.typed -> build/lib.linux-x86_64-cpython-310/breezy running build_ext running build_rust cargo rustc --lib --message-format=json-render-diagnostics --manifest-path lib-rio/Cargo.toml --release -v --features pyo3/extension-module --crate-type cdylib -- Compiling target-lexicon v0.12.11 Compiling autocfg v1.1.0 Compiling once_cell v1.18.0 Compiling proc-macro2 v1.0.66 Compiling libc v0.2.147 Compiling unicode-ident v1.0.11 Compiling syn v1.0.109 Compiling parking_lot_core v0.9.8 Compiling cfg-if v1.0.0 Compiling smallvec v1.11.0 Compiling memchr v2.6.3 Compiling scopeguard v1.2.0 Compiling regex-syntax v0.7.5 Compiling unindent v0.1.11 Compiling indoc v1.0.9 Compiling lazy_static v1.4.0 Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/target-lexicon-0.12.11/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' -C metadata=d6f5d99c0d63f95d -C extra-filename=-d6f5d99c0d63f95d --out-dir /build/breezy-3.3.4/target/release/build/target-lexicon-d6f5d99c0d63f95d -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name autocfg /build/cargo-vendor-dir/autocfg-1.1.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off -C metadata=c2f3d041f4430249 -C extra-filename=-c2f3d041f4430249 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name once_cell --edition=2021 /build/cargo-vendor-dir/once_cell-1.18.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 'feature="race"' --cfg 'feature="std"' -C metadata=297e1e3872953d6f -C extra-filename=-297e1e3872953d6f --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name build_script_build --edition=2021 /build/cargo-vendor-dir/proc-macro2-1.0.66/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="proc-macro"' -C metadata=967025e471764c81 -C extra-filename=-967025e471764c81 --out-dir /build/breezy-3.3.4/target/release/build/proc-macro2-967025e471764c81 -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name build_script_build /build/cargo-vendor-dir/libc-0.2.147/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=3f275bdd19cd623f -C extra-filename=-3f275bdd19cd623f --out-dir /build/breezy-3.3.4/target/release/build/libc-3f275bdd19cd623f -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name unicode_ident --edition=2018 /build/cargo-vendor-dir/unicode-ident-1.0.11/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off -C metadata=e8cdc5331fa7bc82 -C extra-filename=-e8cdc5331fa7bc82 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/syn-1.0.109/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="clone-impls"' --cfg 'feature="default"' --cfg 'feature="derive"' --cfg 'feature="extra-traits"' --cfg 'feature="full"' --cfg 'feature="parsing"' --cfg 'feature="printing"' --cfg 'feature="proc-macro"' --cfg 'feature="quote"' -C metadata=0318fce96958dfdb -C extra-filename=-0318fce96958dfdb --out-dir /build/breezy-3.3.4/target/release/build/syn-0318fce96958dfdb -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/parking_lot_core-0.9.8/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off -C metadata=c8f42911cea0071c -C extra-filename=-c8f42911cea0071c --out-dir /build/breezy-3.3.4/target/release/build/parking_lot_core-c8f42911cea0071c -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name smallvec --edition=2018 /build/cargo-vendor-dir/smallvec-1.11.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=34facdc929a85995 -C extra-filename=-34facdc929a85995 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name cfg_if --edition=2018 /build/cargo-vendor-dir/cfg-if-1.0.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=488b513b090e903d -C extra-filename=-488b513b090e903d --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name memchr --edition=2021 /build/cargo-vendor-dir/memchr-2.6.3/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=d1a774109309e1f3 -C extra-filename=-d1a774109309e1f3 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name scopeguard /build/cargo-vendor-dir/scopeguard-1.2.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=4cad4b6c669eec56 -C extra-filename=-4cad4b6c669eec56 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name regex_syntax --edition=2021 /build/cargo-vendor-dir/regex-syntax-0.7.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="std"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' -C metadata=a395e5d35d390bfc -C extra-filename=-a395e5d35d390bfc --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name unindent --edition=2018 /build/cargo-vendor-dir/unindent-0.1.11/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=2fb5bcaa3e1f253c -C extra-filename=-2fb5bcaa3e1f253c --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name lazy_static /build/cargo-vendor-dir/lazy_static-1.4.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=844df39269fa0ef2 -C extra-filename=-844df39269fa0ef2 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name indoc --edition=2018 /build/cargo-vendor-dir/indoc-1.0.9/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type proc-macro --emit=dep-info,link -C prefer-dynamic -C embed-bitcode=no -C debug-assertions=off -C metadata=558756cda9e0998e -C extra-filename=-558756cda9e0998e --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern proc_macro --cap-lints allow -C target-feature=-crt-static` Compiling lock_api v0.4.10 Compiling memoffset v0.9.0 Running `rustc --crate-name build_script_build /build/cargo-vendor-dir/memoffset-0.9.0/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' -C metadata=706cf641bdab1cd9 -C extra-filename=-706cf641bdab1cd9 --out-dir /build/breezy-3.3.4/target/release/build/memoffset-706cf641bdab1cd9 -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern autocfg=/build/breezy-3.3.4/target/release/deps/libautocfg-c2f3d041f4430249.rlib --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/lock_api-0.4.10/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="atomic_usize"' --cfg 'feature="default"' -C metadata=e76fa8fd4ccd0c35 -C extra-filename=-e76fa8fd4ccd0c35 --out-dir /build/breezy-3.3.4/target/release/build/lock_api-e76fa8fd4ccd0c35 -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern autocfg=/build/breezy-3.3.4/target/release/deps/libautocfg-c2f3d041f4430249.rlib --cap-lints allow -C target-feature=-crt-static` Running `/build/breezy-3.3.4/target/release/build/parking_lot_core-c8f42911cea0071c/build-script-build` Running `/build/breezy-3.3.4/target/release/build/proc-macro2-967025e471764c81/build-script-build` Running `/build/breezy-3.3.4/target/release/build/libc-3f275bdd19cd623f/build-script-build` Running `/build/breezy-3.3.4/target/release/build/syn-0318fce96958dfdb/build-script-build` Running `rustc --crate-name proc_macro2 --edition=2021 /build/cargo-vendor-dir/proc-macro2-1.0.66/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="proc-macro"' -C metadata=74a2e0a7bba3e0e9 -C extra-filename=-74a2e0a7bba3e0e9 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern unicode_ident=/build/breezy-3.3.4/target/release/deps/libunicode_ident-e8cdc5331fa7bc82.rmeta --cap-lints allow -C target-feature=-crt-static --cfg wrap_proc_macro` Running `rustc --crate-name libc /build/cargo-vendor-dir/libc-0.2.147/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=49fa31bc158d587c -C extra-filename=-49fa31bc158d587c --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static --cfg freebsd11 --cfg libc_priv_mod_use --cfg libc_union --cfg libc_const_size_of --cfg libc_align --cfg libc_int128 --cfg libc_core_cvoid --cfg libc_packedN --cfg libc_cfg_target_vendor --cfg libc_non_exhaustive --cfg libc_long_array --cfg libc_ptr_addr_of --cfg libc_underscore_const_names --cfg libc_const_extern_fn` Running `/build/breezy-3.3.4/target/release/build/target-lexicon-d6f5d99c0d63f95d/build-script-build` Running `rustc --crate-name target_lexicon --edition=2018 /build/cargo-vendor-dir/target-lexicon-0.12.11/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' -C metadata=42044c8e9e166fde -C extra-filename=-42044c8e9e166fde --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static --cfg 'feature="rust_1_40"'` Running `/build/breezy-3.3.4/target/release/build/memoffset-706cf641bdab1cd9/build-script-build` Running `/build/breezy-3.3.4/target/release/build/lock_api-e76fa8fd4ccd0c35/build-script-build` Running `rustc --crate-name memoffset /build/cargo-vendor-dir/memoffset-0.9.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' -C metadata=abb2ebf1a81b39bf -C extra-filename=-abb2ebf1a81b39bf --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --cap-lints allow -C target-feature=-crt-static --cfg tuple_ty --cfg allow_clippy --cfg maybe_uninit --cfg doctests --cfg raw_ref_macros --cfg stable_const` Running `rustc --crate-name lock_api --edition=2018 /build/cargo-vendor-dir/lock_api-0.4.10/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="atomic_usize"' --cfg 'feature="default"' -C metadata=029aada2f0af43c7 -C extra-filename=-029aada2f0af43c7 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern scopeguard=/build/breezy-3.3.4/target/release/deps/libscopeguard-4cad4b6c669eec56.rmeta --cap-lints allow -C target-feature=-crt-static --cfg has_const_fn_trait_bound` Compiling aho-corasick v1.0.5 Running `rustc --crate-name aho_corasick --edition=2021 /build/cargo-vendor-dir/aho-corasick-1.0.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="perf-literal"' --cfg 'feature="std"' -C metadata=4878417629b6fdeb -C extra-filename=-4878417629b6fdeb --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern memchr=/build/breezy-3.3.4/target/release/deps/libmemchr-d1a774109309e1f3.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling quote v1.0.33 Running `rustc --crate-name quote --edition=2018 /build/cargo-vendor-dir/quote-1.0.33/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="proc-macro"' -C metadata=0b47706786987fdd -C extra-filename=-0b47706786987fdd --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern proc_macro2=/build/breezy-3.3.4/target/release/deps/libproc_macro2-74a2e0a7bba3e0e9.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling pyo3-build-config v0.19.2 Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/pyo3-build-config-0.19.2/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="extension-module"' --cfg 'feature="resolve-config"' -C metadata=574944d849cfede1 -C extra-filename=-574944d849cfede1 --out-dir /build/breezy-3.3.4/target/release/build/pyo3-build-config-574944d849cfede1 -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern target_lexicon=/build/breezy-3.3.4/target/release/deps/libtarget_lexicon-42044c8e9e166fde.rlib --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name syn --edition=2018 /build/cargo-vendor-dir/syn-1.0.109/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="clone-impls"' --cfg 'feature="default"' --cfg 'feature="derive"' --cfg 'feature="extra-traits"' --cfg 'feature="full"' --cfg 'feature="parsing"' --cfg 'feature="printing"' --cfg 'feature="proc-macro"' --cfg 'feature="quote"' -C metadata=585d5510bd498b08 -C extra-filename=-585d5510bd498b08 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern proc_macro2=/build/breezy-3.3.4/target/release/deps/libproc_macro2-74a2e0a7bba3e0e9.rmeta --extern quote=/build/breezy-3.3.4/target/release/deps/libquote-0b47706786987fdd.rmeta --extern unicode_ident=/build/breezy-3.3.4/target/release/deps/libunicode_ident-e8cdc5331fa7bc82.rmeta --cap-lints allow -C target-feature=-crt-static --cfg syn_disable_nightly_tests` Running `rustc --crate-name parking_lot_core --edition=2018 /build/cargo-vendor-dir/parking_lot_core-0.9.8/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=1444e99c84d89ac6 -C extra-filename=-1444e99c84d89ac6 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern cfg_if=/build/breezy-3.3.4/target/release/deps/libcfg_if-488b513b090e903d.rmeta --extern libc=/build/breezy-3.3.4/target/release/deps/liblibc-49fa31bc158d587c.rmeta --extern smallvec=/build/breezy-3.3.4/target/release/deps/libsmallvec-34facdc929a85995.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling parking_lot v0.12.1 Running `rustc --crate-name parking_lot --edition=2018 /build/cargo-vendor-dir/parking_lot-0.12.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' -C metadata=bb03a9cd174a07b7 -C extra-filename=-bb03a9cd174a07b7 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern lock_api=/build/breezy-3.3.4/target/release/deps/liblock_api-029aada2f0af43c7.rmeta --extern parking_lot_core=/build/breezy-3.3.4/target/release/deps/libparking_lot_core-1444e99c84d89ac6.rmeta --cap-lints allow -C target-feature=-crt-static` Running `/build/breezy-3.3.4/target/release/build/pyo3-build-config-574944d849cfede1/build-script-build` Running `rustc --crate-name pyo3_build_config --edition=2018 /build/cargo-vendor-dir/pyo3-build-config-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="extension-module"' --cfg 'feature="resolve-config"' -C metadata=10c37554c410356e -C extra-filename=-10c37554c410356e --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern once_cell=/build/breezy-3.3.4/target/release/deps/libonce_cell-297e1e3872953d6f.rmeta --extern target_lexicon=/build/breezy-3.3.4/target/release/deps/libtarget_lexicon-42044c8e9e166fde.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling regex-automata v0.3.8 Running `rustc --crate-name regex_automata --edition=2021 /build/cargo-vendor-dir/regex-automata-0.3.8/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="alloc"' --cfg 'feature="dfa-onepass"' --cfg 'feature="hybrid"' --cfg 'feature="meta"' --cfg 'feature="nfa-backtrack"' --cfg 'feature="nfa-pikevm"' --cfg 'feature="nfa-thompson"' --cfg 'feature="perf-inline"' --cfg 'feature="perf-literal"' --cfg 'feature="perf-literal-multisubstring"' --cfg 'feature="perf-literal-substring"' --cfg 'feature="std"' --cfg 'feature="syntax"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' --cfg 'feature="unicode-word-boundary"' -C metadata=af958a76a1b0e0d2 -C extra-filename=-af958a76a1b0e0d2 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern aho_corasick=/build/breezy-3.3.4/target/release/deps/libaho_corasick-4878417629b6fdeb.rmeta --extern memchr=/build/breezy-3.3.4/target/release/deps/libmemchr-d1a774109309e1f3.rmeta --extern regex_syntax=/build/breezy-3.3.4/target/release/deps/libregex_syntax-a395e5d35d390bfc.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling pyo3-ffi v0.19.2 Compiling pyo3 v0.19.2 Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/pyo3-ffi-0.19.2/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="extension-module"' -C metadata=789b57893e6707ea -C extra-filename=-789b57893e6707ea --out-dir /build/breezy-3.3.4/target/release/build/pyo3-ffi-789b57893e6707ea -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern pyo3_build_config=/build/breezy-3.3.4/target/release/deps/libpyo3_build_config-10c37554c410356e.rlib --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/pyo3-0.19.2/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="extension-module"' --cfg 'feature="indoc"' --cfg 'feature="macros"' --cfg 'feature="pyo3-macros"' --cfg 'feature="unindent"' -C metadata=98edd516d74ff286 -C extra-filename=-98edd516d74ff286 --out-dir /build/breezy-3.3.4/target/release/build/pyo3-98edd516d74ff286 -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern pyo3_build_config=/build/breezy-3.3.4/target/release/deps/libpyo3_build_config-10c37554c410356e.rlib --cap-lints allow -C target-feature=-crt-static` Running `/build/breezy-3.3.4/target/release/build/pyo3-ffi-789b57893e6707ea/build-script-build` Running `rustc --crate-name pyo3_ffi --edition=2018 /build/cargo-vendor-dir/pyo3-ffi-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="extension-module"' -C metadata=5065bd8d5849c0ec -C extra-filename=-5065bd8d5849c0ec --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern libc=/build/breezy-3.3.4/target/release/deps/liblibc-49fa31bc158d587c.rmeta --cap-lints allow -C target-feature=-crt-static --cfg Py_3_6 --cfg Py_3_7 --cfg Py_3_8 --cfg Py_3_9 --cfg Py_3_10 --cfg min_const_generics --cfg addr_of --cfg option_insert --cfg thread_local_const_init --cfg panic_unwind` Running `/build/breezy-3.3.4/target/release/build/pyo3-98edd516d74ff286/build-script-build` Compiling pyo3-macros-backend v0.19.2 Running `rustc --crate-name pyo3_macros_backend --edition=2018 /build/cargo-vendor-dir/pyo3-macros-backend-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off -C metadata=861452faaa697ece -C extra-filename=-861452faaa697ece --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern proc_macro2=/build/breezy-3.3.4/target/release/deps/libproc_macro2-74a2e0a7bba3e0e9.rmeta --extern quote=/build/breezy-3.3.4/target/release/deps/libquote-0b47706786987fdd.rmeta --extern syn=/build/breezy-3.3.4/target/release/deps/libsyn-585d5510bd498b08.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling regex v1.9.5 Running `rustc --crate-name regex --edition=2021 /build/cargo-vendor-dir/regex-1.9.5/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="perf"' --cfg 'feature="perf-backtrack"' --cfg 'feature="perf-cache"' --cfg 'feature="perf-dfa"' --cfg 'feature="perf-inline"' --cfg 'feature="perf-literal"' --cfg 'feature="perf-onepass"' --cfg 'feature="std"' --cfg 'feature="unicode"' --cfg 'feature="unicode-age"' --cfg 'feature="unicode-bool"' --cfg 'feature="unicode-case"' --cfg 'feature="unicode-gencat"' --cfg 'feature="unicode-perl"' --cfg 'feature="unicode-script"' --cfg 'feature="unicode-segment"' -C metadata=8169f6be1b21a859 -C extra-filename=-8169f6be1b21a859 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern aho_corasick=/build/breezy-3.3.4/target/release/deps/libaho_corasick-4878417629b6fdeb.rmeta --extern memchr=/build/breezy-3.3.4/target/release/deps/libmemchr-d1a774109309e1f3.rmeta --extern regex_automata=/build/breezy-3.3.4/target/release/deps/libregex_automata-af958a76a1b0e0d2.rmeta --extern regex_syntax=/build/breezy-3.3.4/target/release/deps/libregex_syntax-a395e5d35d390bfc.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling pyo3-macros v0.19.2 Running `rustc --crate-name pyo3_macros --edition=2018 /build/cargo-vendor-dir/pyo3-macros-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type proc-macro --emit=dep-info,link -C prefer-dynamic -C embed-bitcode=no -C debug-assertions=off -C metadata=5df5c84876befde8 -C extra-filename=-5df5c84876befde8 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern proc_macro2=/build/breezy-3.3.4/target/release/deps/libproc_macro2-74a2e0a7bba3e0e9.rlib --extern pyo3_macros_backend=/build/breezy-3.3.4/target/release/deps/libpyo3_macros_backend-861452faaa697ece.rlib --extern quote=/build/breezy-3.3.4/target/release/deps/libquote-0b47706786987fdd.rlib --extern syn=/build/breezy-3.3.4/target/release/deps/libsyn-585d5510bd498b08.rlib --extern proc_macro --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name pyo3 --edition=2018 /build/cargo-vendor-dir/pyo3-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="extension-module"' --cfg 'feature="indoc"' --cfg 'feature="macros"' --cfg 'feature="pyo3-macros"' --cfg 'feature="unindent"' -C metadata=ca658432bf906c2b -C extra-filename=-ca658432bf906c2b --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern cfg_if=/build/breezy-3.3.4/target/release/deps/libcfg_if-488b513b090e903d.rmeta --extern indoc=/build/breezy-3.3.4/target/release/deps/libindoc-558756cda9e0998e.so --extern libc=/build/breezy-3.3.4/target/release/deps/liblibc-49fa31bc158d587c.rmeta --extern memoffset=/build/breezy-3.3.4/target/release/deps/libmemoffset-abb2ebf1a81b39bf.rmeta --extern parking_lot=/build/breezy-3.3.4/target/release/deps/libparking_lot-bb03a9cd174a07b7.rmeta --extern pyo3_ffi=/build/breezy-3.3.4/target/release/deps/libpyo3_ffi-5065bd8d5849c0ec.rmeta --extern pyo3_macros=/build/breezy-3.3.4/target/release/deps/libpyo3_macros-5df5c84876befde8.so --extern unindent=/build/breezy-3.3.4/target/release/deps/libunindent-2fb5bcaa3e1f253c.rmeta --cap-lints allow -C target-feature=-crt-static --cfg Py_3_6 --cfg Py_3_7 --cfg Py_3_8 --cfg Py_3_9 --cfg Py_3_10 --cfg min_const_generics --cfg addr_of --cfg option_insert --cfg thread_local_const_init --cfg panic_unwind` Compiling rio-py v3.3.4 (/build/breezy-3.3.4/lib-rio) Running `rustc --crate-name rio --edition=2018 lib-rio/pyrio.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type cdylib --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C metadata=93477832007d7fce --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern lazy_static=/build/breezy-3.3.4/target/release/deps/liblazy_static-844df39269fa0ef2.rlib --extern pyo3=/build/breezy-3.3.4/target/release/deps/libpyo3-ca658432bf906c2b.rlib --extern regex=/build/breezy-3.3.4/target/release/deps/libregex-8169f6be1b21a859.rlib -C target-feature=-crt-static` Finished release [optimized] target(s) in 11.55s Copying rust artifact from /build/breezy-3.3.4/target/release/librio.so to build/lib.linux-x86_64-cpython-310/breezy/bzr/_rio_rs.cpython-310-x86_64-linux-gnu.so cargo build --manifest-path Cargo.toml --message-format=json-render-diagnostics --release -v Fresh target-lexicon v0.12.11 Fresh autocfg v1.1.0 Fresh once_cell v1.18.0 Fresh unicode-ident v1.0.11 Fresh smallvec v1.11.0 Fresh cfg-if v1.0.0 Fresh scopeguard v1.2.0 Fresh indoc v1.0.9 Fresh unindent v0.1.11 Compiling pyo3-build-config v0.19.2 Fresh proc-macro2 v1.0.66 Fresh libc v0.2.147 Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/pyo3-build-config-0.19.2/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="resolve-config"' -C metadata=97ea40ff7868b926 -C extra-filename=-97ea40ff7868b926 --out-dir /build/breezy-3.3.4/target/release/build/pyo3-build-config-97ea40ff7868b926 -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern target_lexicon=/build/breezy-3.3.4/target/release/deps/libtarget_lexicon-42044c8e9e166fde.rlib --cap-lints allow -C target-feature=-crt-static` Fresh quote v1.0.33 Fresh lock_api v0.4.10 Fresh parking_lot_core v0.9.8 Fresh memoffset v0.9.0 Fresh syn v1.0.109 Fresh parking_lot v0.12.1 Fresh pyo3-macros-backend v0.19.2 Fresh pyo3-macros v0.19.2 Running `/build/breezy-3.3.4/target/release/build/pyo3-build-config-97ea40ff7868b926/build-script-build` Running `rustc --crate-name pyo3_build_config --edition=2018 /build/cargo-vendor-dir/pyo3-build-config-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="resolve-config"' -C metadata=a843c8fa8fe821ad -C extra-filename=-a843c8fa8fe821ad --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern once_cell=/build/breezy-3.3.4/target/release/deps/libonce_cell-297e1e3872953d6f.rmeta --extern target_lexicon=/build/breezy-3.3.4/target/release/deps/libtarget_lexicon-42044c8e9e166fde.rmeta --cap-lints allow -C target-feature=-crt-static` Compiling pyo3-ffi v0.19.2 Compiling pyo3 v0.19.2 Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/pyo3-ffi-0.19.2/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' -C metadata=6c00c5100a126f9f -C extra-filename=-6c00c5100a126f9f --out-dir /build/breezy-3.3.4/target/release/build/pyo3-ffi-6c00c5100a126f9f -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern pyo3_build_config=/build/breezy-3.3.4/target/release/deps/libpyo3_build_config-a843c8fa8fe821ad.rlib --cap-lints allow -C target-feature=-crt-static` Running `rustc --crate-name build_script_build --edition=2018 /build/cargo-vendor-dir/pyo3-0.19.2/build.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debug-assertions=off --cfg 'feature="default"' --cfg 'feature="indoc"' --cfg 'feature="macros"' --cfg 'feature="pyo3-macros"' --cfg 'feature="unindent"' -C metadata=8e85ce59b2c384ef -C extra-filename=-8e85ce59b2c384ef --out-dir /build/breezy-3.3.4/target/release/build/pyo3-8e85ce59b2c384ef -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern pyo3_build_config=/build/breezy-3.3.4/target/release/deps/libpyo3_build_config-a843c8fa8fe821ad.rlib --cap-lints allow -C target-feature=-crt-static` Running `/build/breezy-3.3.4/target/release/build/pyo3-ffi-6c00c5100a126f9f/build-script-build` Running `/build/breezy-3.3.4/target/release/build/pyo3-8e85ce59b2c384ef/build-script-build` Running `rustc --crate-name pyo3_ffi --edition=2018 /build/cargo-vendor-dir/pyo3-ffi-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' -C metadata=6342c80fb985d4d4 -C extra-filename=-6342c80fb985d4d4 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern libc=/build/breezy-3.3.4/target/release/deps/liblibc-49fa31bc158d587c.rmeta --cap-lints allow -C target-feature=-crt-static -L native=/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -l python3.10 --cfg Py_3_6 --cfg Py_3_7 --cfg Py_3_8 --cfg Py_3_9 --cfg Py_3_10 --cfg min_const_generics --cfg addr_of --cfg option_insert --cfg thread_local_const_init --cfg panic_unwind` Running `rustc --crate-name pyo3 --edition=2018 /build/cargo-vendor-dir/pyo3-0.19.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="indoc"' --cfg 'feature="macros"' --cfg 'feature="pyo3-macros"' --cfg 'feature="unindent"' -C metadata=d66978e4ea48ea90 -C extra-filename=-d66978e4ea48ea90 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern cfg_if=/build/breezy-3.3.4/target/release/deps/libcfg_if-488b513b090e903d.rmeta --extern indoc=/build/breezy-3.3.4/target/release/deps/libindoc-558756cda9e0998e.so --extern libc=/build/breezy-3.3.4/target/release/deps/liblibc-49fa31bc158d587c.rmeta --extern memoffset=/build/breezy-3.3.4/target/release/deps/libmemoffset-abb2ebf1a81b39bf.rmeta --extern parking_lot=/build/breezy-3.3.4/target/release/deps/libparking_lot-bb03a9cd174a07b7.rmeta --extern pyo3_ffi=/build/breezy-3.3.4/target/release/deps/libpyo3_ffi-6342c80fb985d4d4.rmeta --extern pyo3_macros=/build/breezy-3.3.4/target/release/deps/libpyo3_macros-5df5c84876befde8.so --extern unindent=/build/breezy-3.3.4/target/release/deps/libunindent-2fb5bcaa3e1f253c.rmeta --cap-lints allow -C target-feature=-crt-static -L native=/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib --cfg Py_3_6 --cfg Py_3_7 --cfg Py_3_8 --cfg Py_3_9 --cfg Py_3_10 --cfg min_const_generics --cfg addr_of --cfg option_insert --cfg thread_local_const_init --cfg panic_unwind` Compiling breezy v3.3.4 (/build/breezy-3.3.4) Running `rustc --crate-name brz --edition=2018 breezy/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=3 -C embed-bitcode=no -C metadata=c5e570a25a43c724 -C extra-filename=-c5e570a25a43c724 --out-dir /build/breezy-3.3.4/target/release/deps -C linker=/nix/store/18bs92p6yf6w2wwxhbplgx02y6anq092-gcc-wrapper-12.3.0/bin/cc -L dependency=/build/breezy-3.3.4/target/release/deps --extern pyo3=/build/breezy-3.3.4/target/release/deps/libpyo3-d66978e4ea48ea90.rlib -C target-feature=-crt-static -L native=/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib` Finished release [optimized] target(s) in 5.29s Copying rust artifact from /build/breezy-3.3.4/target/release/brz to build/lib.linux-x86_64-cpython-310/brz skipping 'breezy/bzr/_simple_set_pyx.c' Cython extension (up-to-date) skipping 'breezy/_annotator_pyx.c' Cython extension (up-to-date) skipping 'breezy/_chunks_to_lines_pyx.c' Cython extension (up-to-date) skipping 'breezy/bzr/_groupcompress_pyx.c' Cython extension (up-to-date) skipping 'breezy/bzr/_knit_load_data_pyx.c' Cython extension (up-to-date) skipping 'breezy/_known_graph_pyx.c' Cython extension (up-to-date) skipping 'breezy/bzr/_rio_pyx.c' Cython extension (up-to-date) skipping 'breezy/bzr/_dirstate_helpers_pyx.c' Cython extension (up-to-date) skipping 'breezy/_readdir_pyx.c' Cython extension (up-to-date) skipping 'breezy/bzr/_chk_map_pyx.c' Cython extension (up-to-date) skipping 'breezy/bzr/_btree_serializer_pyx.c' Cython extension (up-to-date) building 'breezy.bzr._simple_set_pyx' extension creating build/temp.linux-x86_64-cpython-310 creating build/temp.linux-x86_64-cpython-310/breezy creating build/temp.linux-x86_64-cpython-310/breezy/bzr gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_simple_set_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_simple_set_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_simple_set_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_simple_set_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy.bzr._static_tuple_c' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_static_tuple_c.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_static_tuple_c.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_static_tuple_c.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_static_tuple_c.cpython-310-x86_64-linux-gnu.so building 'breezy._annotator_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/_annotator_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/_annotator_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/_annotator_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/_annotator_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy._chunks_to_lines_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/_chunks_to_lines_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/_chunks_to_lines_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/_chunks_to_lines_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/_chunks_to_lines_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy.bzr._groupcompress_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_groupcompress_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_groupcompress_pyx.o gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/diff-delta.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/diff-delta.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_groupcompress_pyx.o build/temp.linux-x86_64-cpython-310/breezy/bzr/diff-delta.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_groupcompress_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy.bzr._knit_load_data_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_knit_load_data_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_knit_load_data_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_knit_load_data_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_knit_load_data_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy._known_graph_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/_known_graph_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/_known_graph_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/_known_graph_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/_known_graph_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy.bzr._rio_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_rio_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_rio_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_rio_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_rio_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy.bzr._dirstate_helpers_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_dirstate_helpers_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_dirstate_helpers_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_dirstate_helpers_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_dirstate_helpers_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy._readdir_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/_readdir_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/_readdir_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/_readdir_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/_readdir_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy.bzr._chk_map_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_chk_map_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_chk_map_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_chk_map_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_chk_map_pyx.cpython-310-x86_64-linux-gnu.so building 'breezy.bzr._btree_serializer_pyx' extension gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -I/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/include -fPIC -Ibreezy -I/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/include/python3.10 -c breezy/bzr/_btree_serializer_pyx.c -o build/temp.linux-x86_64-cpython-310/breezy/bzr/_btree_serializer_pyx.o gcc -shared -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-zlib-1.3/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-bzip2-1.0.8/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-expat-2.5.0/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-xz-5.4.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-libffi-3.4.4/lib -L/nix/store/ml12av0bi52w2nyrpay8l47xwm1m6i7b-libxcrypt-4.4.36/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-gdbm-1.23/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-sqlite-3.43.1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-readline-8.2p1/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-ncurses-6.4/lib -L/nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-openssl-3.0.10/lib -L/nix/store/dk5vk3c9zknbjzzxmiglzv46qgv32gb0-tzdata-2023c/lib build/temp.linux-x86_64-cpython-310/breezy/bzr/_btree_serializer_pyx.o -L/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/lib -o build/lib.linux-x86_64-cpython-310/breezy/bzr/_btree_serializer_pyx.cpython-310-x86_64-linux-gnu.so running build_scripts creating build/scripts-3.10 copying and adjusting breezy/git/git-remote-bzr -> build/scripts-3.10 copying and adjusting breezy/git/bzr-receive-pack -> build/scripts-3.10 copying and adjusting breezy/git/bzr-upload-pack -> build/scripts-3.10 changing mode of build/scripts-3.10/git-remote-bzr from 644 to 755 changing mode of build/scripts-3.10/bzr-receive-pack from 644 to 755 changing mode of build/scripts-3.10/bzr-upload-pack from 644 to 755 running build_mo GNU gettext msgfmt utility not found! Skip compiling po files. installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/symbol_versioning.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/revisiontree.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/patch.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/externalcommand.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/cmd_test_script.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/archive copying build/lib.linux-x86_64-cpython-310/breezy/archive/tar.py -> build/bdist.linux-x86_64/wheel/breezy/archive copying build/lib.linux-x86_64-cpython-310/breezy/archive/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/archive copying build/lib.linux-x86_64-cpython-310/breezy/archive/zip.py -> build/bdist.linux-x86_64/wheel/breezy/archive copying build/lib.linux-x86_64-cpython-310/breezy/_readdir_py.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/lazy_regex.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/mutabletree.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/textmerge.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/decorators.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/timestamp.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/library_state.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/location.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/send.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/transactions.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/memorybranch.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/treebuilder.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/trace.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/missing.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/views.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/repository.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/filters copying build/lib.linux-x86_64-cpython-310/breezy/filters/eol.py -> build/bdist.linux-x86_64/wheel/breezy/filters copying build/lib.linux-x86_64-cpython-310/breezy/filters/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/filters copying build/lib.linux-x86_64-cpython-310/breezy/textfile.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/pack.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/check.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/knitrepo.py -> build/bdist.linux-x86_64/wheel/breezy/bzr creating build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/packrepository.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/medium.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/vfs.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/server.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/branch.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/protocol.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/client.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/message.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/signals.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/bzrdir.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/ping.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/repository.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/request.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/smart/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/smart copying build/lib.linux-x86_64-cpython-310/breezy/bzr/remote.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/weavefile.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/inventory_delta.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_groupcompress_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/conflicts.py -> build/bdist.linux-x86_64/wheel/breezy/bzr creating build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_chk_map.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_groupcompress.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_workingtree_4.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_xml.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_chk_serializer.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_remote.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_rio.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_matchers.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_tag.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_vf_search.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_versionedfile.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_inv.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_inventory_delta.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_pack.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_testament.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_smart_transport.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests creating build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_fileid_involved.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_check_reconcile.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_write_group.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_find_text_key_references.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_check.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test__generate_text_key_index.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_refresh_data.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_reconcile.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_add_inventory_by_delta.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_repository.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_fetch.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/test_merge_directive.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/helpers.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_vf/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_vf copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_hashcache.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/matchers.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests creating build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_inventory copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_inventory/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_inventory copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_inventory/basics.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_inventory copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_bzrdir.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_index.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests creating build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_chk copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_chk/test_supported.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_chk copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_chk/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_chk copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_repository_chk/test_unsupported.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_repository_chk copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_dirstate.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_bundle.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_knit.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_conflicts.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test__simple_set.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test__dirstate_helpers.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_tuned_gzip.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_smart.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_smart_request.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests creating build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_bzrdir copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_bzrdir/test_bzrdir.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_bzrdir copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_bzrdir/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/per_bzrdir copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests creating build/bdist.linux-x86_64/wheel/breezy/bzr/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/blackbox/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/blackbox/test_dump_btree.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_versionedfile.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_btree_index.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test__chk_map.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test__rio.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_repository.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_weave.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_transform.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_serializer.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_generate_ids.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_vfs_ratchet.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/per_pack_repository.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_smart_signals.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test_read_bundle.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test__btree_serializer.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test__groupcompress.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tests/test__static_tuple.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/tests copying build/lib.linux-x86_64-cpython-310/breezy/bzr/textinv.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/chk_map.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/recordcounter.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/inventory.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/xml8.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/index.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/workingtree_4.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/groupcompress.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/generate_ids.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/static_tuple.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/debug_commands.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/knitpack_repo.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_dirstate_helpers_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/xml_serializer.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/branch.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/transform.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/weave.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/versionedfile.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_static_tuple_c.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/vf_repository.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/inventorytree.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/reconcile.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_static_tuple_py.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_rio_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_knit_load_data_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/workingtree_3.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/repository.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/xml6.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/bzr creating build/bdist.linux-x86_64/wheel/breezy/bzr/bundle copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/apply_bundle.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/bundle_data.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle creating build/bdist.linux-x86_64/wheel/breezy/bzr/bundle/serializer copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer/v4.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle/serializer copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer/v09.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle/serializer copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer/v08.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle/serializer copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/serializer/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle/serializer copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bundle/commands.py -> build/bdist.linux-x86_64/wheel/breezy/bzr/bundle copying build/lib.linux-x86_64-cpython-310/breezy/bzr/serializer.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/groupcompress_repo.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/chk_serializer.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/xml7.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/dirstate.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/xml5.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_btree_serializer_py.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/bzrdir.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/fetch.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/rio.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_chk_map_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_simple_set_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_groupcompress_py.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/fullhistory.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tag.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/vf_search.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_chk_map_py.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/tuned_gzip.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/testament.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/pack_repo.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_btree_serializer_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_rio_py.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/btree_index.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_rio_rs.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/knit.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_knit_load_data_py.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/hashcache.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/bzr/_dirstate_helpers_py.py -> build/bdist.linux-x86_64/wheel/breezy/bzr copying build/lib.linux-x86_64-cpython-310/breezy/cethread.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/patches.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/bisect_multi.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/fifo_cache.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/branchbuilder.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/crash.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/upgrade.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/directory_service.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/diff.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/py.typed -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/forge.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/log.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/__init__.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/tag.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/strace.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/gpg.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/delta.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/identitymap.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/url_policy_open.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/inter.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/lockdir.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/fetch_ghosts.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/export.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/annotate.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/_annotator_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/workingtree.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/lock.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/urlutils.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/info.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/registry.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/progress.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/commit_signature_commands.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/merge_directive.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/revision.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/switch.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/revisionspec.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/tsort.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/grep.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/ignores.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/_readdir_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/ui copying build/lib.linux-x86_64-cpython-310/breezy/ui/text.py -> build/bdist.linux-x86_64/wheel/breezy/ui copying build/lib.linux-x86_64-cpython-310/breezy/ui/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/ui copying build/lib.linux-x86_64-cpython-310/breezy/status.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/lsprof.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/atomicfile.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/config.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/bedding.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/doc_generate copying build/lib.linux-x86_64-cpython-310/breezy/doc_generate/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/doc_generate copying build/lib.linux-x86_64-cpython-310/breezy/doc_generate/autodoc_bash_completion.py -> build/bdist.linux-x86_64/wheel/breezy/doc_generate copying build/lib.linux-x86_64-cpython-310/breezy/doc_generate/autodoc_rstx.py -> build/bdist.linux-x86_64/wheel/breezy/doc_generate copying build/lib.linux-x86_64-cpython-310/breezy/doc_generate/autodoc_man.py -> build/bdist.linux-x86_64/wheel/breezy/doc_generate copying build/lib.linux-x86_64-cpython-310/breezy/doc_generate/conf.py -> build/bdist.linux-x86_64/wheel/breezy/doc_generate copying build/lib.linux-x86_64-cpython-310/breezy/_termcolor.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/osutils.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/hooks.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/foreign.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/shellcomplete.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/mergeable.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/_chunks_to_lines_py.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/memorytree.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/rename_map.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/uncommit.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/graph.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/chunk_writer.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/commands.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/transform.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/breakin.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/shelf.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/plugins creating build/bdist.linux-x86_64/wheel/breezy/plugins/mtn copying build/lib.linux-x86_64-cpython-310/breezy/plugins/mtn/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/mtn creating build/bdist.linux-x86_64/wheel/breezy/plugins/cvs copying build/lib.linux-x86_64-cpython-310/breezy/plugins/cvs/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/cvs creating build/bdist.linux-x86_64/wheel/breezy/plugins/upload copying build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/cmds.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/upload creating build/bdist.linux-x86_64/wheel/breezy/plugins/upload/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/upload/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/tests/test_upload.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/upload/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/tests/test_auto_upload_hook.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/upload/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/upload/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/upload creating build/bdist.linux-x86_64/wheel/breezy/plugins/news_merge copying build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/news_merge copying build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/parser.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/news_merge copying build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/news_merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/news_merge creating build/bdist.linux-x86_64/wheel/breezy/plugins/news_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/tests/test_news_merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/news_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/news_merge/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/news_merge/tests creating build/bdist.linux-x86_64/wheel/breezy/plugins/bash_completion copying build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/bash_completion creating build/bdist.linux-x86_64/wheel/breezy/plugins/bash_completion/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion/tests/test_bashcomp.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/bash_completion/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/bash_completion/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/bash_completion/bashcomp.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/bash_completion creating build/bdist.linux-x86_64/wheel/breezy/plugins/propose copying build/lib.linux-x86_64-cpython-310/breezy/plugins/propose/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/propose creating build/bdist.linux-x86_64/wheel/breezy/plugins/propose/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/propose/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/propose/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/propose/cmds.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/propose creating build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/cmds.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/lp_api.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/account.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/test_account.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/test_lp_api.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/lp_directory.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/test_lp_directory.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/uris.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/test_lp_login.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad copying build/lib.linux-x86_64-cpython-310/breezy/plugins/launchpad/forge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/launchpad creating build/bdist.linux-x86_64/wheel/breezy/plugins/github copying build/lib.linux-x86_64-cpython-310/breezy/plugins/github/cmds.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/github creating build/bdist.linux-x86_64/wheel/breezy/plugins/github/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/github/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/github/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/github/tests/test_forge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/github/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/github/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/github copying build/lib.linux-x86_64-cpython-310/breezy/plugins/github/forge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/github creating build/bdist.linux-x86_64/wheel/breezy/plugins/po_merge copying build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/po_merge creating build/bdist.linux-x86_64/wheel/breezy/plugins/po_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/po_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge/tests/test_po_merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/po_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/po_merge/po_merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/po_merge creating build/bdist.linux-x86_64/wheel/breezy/plugins/gitlab copying build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/forge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/gitlab copying build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/cmds.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/gitlab copying build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/gitlab creating build/bdist.linux-x86_64/wheel/breezy/plugins/gitlab/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/gitlab/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/gitlab/tests/test_forge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/gitlab/tests creating build/bdist.linux-x86_64/wheel/breezy/plugins/fossil copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fossil/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fossil creating build/bdist.linux-x86_64/wheel/breezy/plugins/quilt creating build/bdist.linux-x86_64/wheel/breezy/plugins/quilt/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/tests/test_wrapper.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/quilt/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/tests/test_merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/quilt/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/quilt/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/quilt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/quilt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/wrapper.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/quilt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/quilt/quilt.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/quilt creating build/bdist.linux-x86_64/wheel/breezy/plugins/hg copying build/lib.linux-x86_64-cpython-310/breezy/plugins/hg/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/hg creating build/bdist.linux-x86_64/wheel/breezy/plugins/pypi copying build/lib.linux-x86_64-cpython-310/breezy/plugins/pypi/directory.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/pypi copying build/lib.linux-x86_64-cpython-310/breezy/plugins/pypi/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/pypi creating build/bdist.linux-x86_64/wheel/breezy/plugins/changelog_merge creating build/bdist.linux-x86_64/wheel/breezy/plugins/changelog_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge/tests/test_changelog_merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/changelog_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/changelog_merge/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge/changelog_merge.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/changelog_merge copying build/lib.linux-x86_64-cpython-310/breezy/plugins/changelog_merge/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/changelog_merge creating build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/repo_keys.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/fetch_all_records.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/missing_keys_for_stacking_fixer.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/chk_used_by.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug creating build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/check_chk.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/file_refs.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug copying build/lib.linux-x86_64-cpython-310/breezy/plugins/repodebug/repo_has_key.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/repodebug creating build/bdist.linux-x86_64/wheel/breezy/plugins/svn copying build/lib.linux-x86_64-cpython-310/breezy/plugins/svn/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/svn copying build/lib.linux-x86_64-cpython-310/breezy/plugins/svn/revspec.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/svn creating build/bdist.linux-x86_64/wheel/breezy/plugins/darcs copying build/lib.linux-x86_64-cpython-310/breezy/plugins/darcs/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/darcs creating build/bdist.linux-x86_64/wheel/breezy/plugins/stats copying build/lib.linux-x86_64-cpython-310/breezy/plugins/stats/test_stats.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/stats copying build/lib.linux-x86_64-cpython-310/breezy/plugins/stats/test_classify.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/stats copying build/lib.linux-x86_64-cpython-310/breezy/plugins/stats/test_blackbox.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/stats copying build/lib.linux-x86_64-cpython-310/breezy/plugins/stats/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/stats copying build/lib.linux-x86_64-cpython-310/breezy/plugins/stats/classify.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/stats copying build/lib.linux-x86_64-cpython-310/breezy/plugins/stats/cmds.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/stats creating build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport creating build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/test_exporter.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/test_commands.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/test_head_tracking.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/test_branch_mapper.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/test_revision_store.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/test_marks_file.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/tests/test_generic_processor.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/marks_file.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/revision_store.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/bzr_commit_handler.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/idmapfile.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/user_mapper.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/exporter.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/helpers.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/branch_mapper.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/branch_updater.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport creating build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/processors copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/processors/generic_processor.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/processors copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/processors/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport/processors copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/cmds.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport copying build/lib.linux-x86_64-cpython-310/breezy/plugins/fastimport/cache_manager.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/fastimport creating build/bdist.linux-x86_64/wheel/breezy/plugins/zsh_completion copying build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion/zshcomp.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/zsh_completion copying build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/zsh_completion creating build/bdist.linux-x86_64/wheel/breezy/plugins/zsh_completion/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion/tests/test_zshcomp.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/zsh_completion/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/zsh_completion/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/zsh_completion/tests creating build/bdist.linux-x86_64/wheel/breezy/plugins/netrc_credential_store copying build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/netrc_credential_store creating build/bdist.linux-x86_64/wheel/breezy/plugins/netrc_credential_store/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store/tests/test_netrc.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/netrc_credential_store/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/netrc_credential_store/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/netrc_credential_store/tests creating build/bdist.linux-x86_64/wheel/breezy/plugins/flake8 copying build/lib.linux-x86_64-cpython-310/breezy/plugins/flake8/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/flake8 creating build/bdist.linux-x86_64/wheel/breezy/plugins/email creating build/bdist.linux-x86_64/wheel/breezy/plugins/email/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/email/tests/testemail.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/email/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/email/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/email/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/email/emailer.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/email copying build/lib.linux-x86_64-cpython-310/breezy/plugins/email/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/email creating build/bdist.linux-x86_64/wheel/breezy/plugins/webdav creating build/bdist.linux-x86_64/wheel/breezy/plugins/webdav/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/tests/dav_server.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/webdav/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/webdav/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/tests/test_webdav.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/webdav/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/webdav copying build/lib.linux-x86_64-cpython-310/breezy/plugins/webdav/webdav.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/webdav creating build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/pseudonyms.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/commands.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/rebase.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/maptree.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite creating build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests/test_blackbox.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests/test_rebase.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests/test_pseudonyms.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests/test_maptree.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests/test_upgrade.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/rewrite/upgrade.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/rewrite creating build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt creating build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt/store copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/store/versioned.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt/store copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/store/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt/store copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/store/text.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt/store copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/bzrdir.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/test_bzrdir.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/test_repository.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/test_workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/repository.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/test_store.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/xml4.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/weave_fmt/branch.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/weave_fmt copying build/lib.linux-x86_64-cpython-310/breezy/plugins/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins creating build/bdist.linux-x86_64/wheel/breezy/plugins/commitfromnews creating build/bdist.linux-x86_64/wheel/breezy/plugins/commitfromnews/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/tests/test_committemplate.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/commitfromnews/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/commitfromnews/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/tests/test_msgeditor.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/commitfromnews/tests copying build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/committemplate.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/commitfromnews copying build/lib.linux-x86_64-cpython-310/breezy/plugins/commitfromnews/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/plugins/commitfromnews copying build/lib.linux-x86_64-cpython-310/breezy/mergetools.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/merge.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/rules.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/filter_tree.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/cmdline.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/option.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/_known_graph_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/__main__.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/win32utils.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/email_message.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/branch.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/multiparent.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/debug.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/tree.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/revspec.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/help.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/push.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/pristine_tar.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/unpeel_map.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/dir.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/config.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/tree.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/hg.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/git_remote_helper.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/filegraph.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/roundtrip.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/fetch.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/annotate.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/repository.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/urls.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/mapping.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/directory.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/cache.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/refs.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/commands.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/object_store.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/errors.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/commit.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/transportgit.py -> build/bdist.linux-x86_64/wheel/breezy/git creating build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_remote.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_git_remote_helper.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_push.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_blackbox.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_transportgit.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_memorytree.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_object_store.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_dir.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_transform.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_cache.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_branch.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_tree.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_builder.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_server.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_revspec.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_urls.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_pristine_tar.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_fetch.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_refs.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_repository.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_mapping.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_unpeel_map.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/tests/test_roundtrip.py -> build/bdist.linux-x86_64/wheel/breezy/git/tests copying build/lib.linux-x86_64-cpython-310/breezy/git/remote.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/server.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/memorytree.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/interrepo.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/branch.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/transform.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/git/send.py -> build/bdist.linux-x86_64/wheel/breezy/git copying build/lib.linux-x86_64-cpython-310/breezy/globbing.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/colordiff.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/brokenrename.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/trace.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/local.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/remote.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/gio_transport.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/readonly.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/nosmart.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/fakevfat.py -> build/bdist.linux-x86_64/wheel/breezy/transport creating build/bdist.linux-x86_64/wheel/breezy/transport/http copying build/lib.linux-x86_64-cpython-310/breezy/transport/http/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/transport/http copying build/lib.linux-x86_64-cpython-310/breezy/transport/http/response.py -> build/bdist.linux-x86_64/wheel/breezy/transport/http copying build/lib.linux-x86_64-cpython-310/breezy/transport/http/ca_bundle.py -> build/bdist.linux-x86_64/wheel/breezy/transport/http copying build/lib.linux-x86_64-cpython-310/breezy/transport/http/urllib.py -> build/bdist.linux-x86_64/wheel/breezy/transport/http copying build/lib.linux-x86_64-cpython-310/breezy/transport/http/wsgi.py -> build/bdist.linux-x86_64/wheel/breezy/transport/http copying build/lib.linux-x86_64-cpython-310/breezy/transport/memory.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/unlistable.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/fakenfs.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/decorator.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/sftp.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/chroot.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/pathfilter.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/ssh.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/transport/log.py -> build/bdist.linux-x86_64/wheel/breezy/transport copying build/lib.linux-x86_64-cpython-310/breezy/clean_tree.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/workspace.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/reconcile.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/plugin.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_urlutils.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_cmdline.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_views.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_fifo_cache.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_link_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_remove.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_export.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_patch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_remember_option.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_split.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_ignore.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_non_ascii.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_uncommit.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_verify_signatures.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_command_encoding.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_bound_branches.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_filtered_view_ops.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_init.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_remove_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_status.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_shared_repository.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_revert.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_script.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_break_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_find_merge_base.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_remerge.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_resolve_location.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_shell_complete.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_re_sign.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_switch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_lookup_revision.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_conflicts.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_serve.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_config.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_inventory.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_import.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_lsprof.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_reference.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_selftest.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_mkdir.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_reconfigure.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_ancestry.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_plugins.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_shelve.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_revision_history.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_added.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_filesystem_cicp.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_revision_info.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_whoami.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_cat.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_reconcile.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_nick.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_modified.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_add.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_versioning.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_unknowns.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_version.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_alias.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_push.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_tags.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_too_much.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_hooks.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_exceptions.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_update.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_help.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_outside_wt.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_send.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_export_pot.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_join.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_cp.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_locale.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_rmbranch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_missing.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_merge.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_fetch_ghosts.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_bisect.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_debug.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_pack.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_diff.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_sign_my_commits.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_log.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_deleted.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_upgrade.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_repair_workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_commit.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_version_info.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_mv.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_clone.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_checkout.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_testament.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_info.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_view.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_revno.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_bundle_info.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_branches.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_annotate.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_pull.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_check.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_big_file.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_cat_revision.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_branch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_resolve.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_ls.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_aliases.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_merge_directive.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_ignored.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_logformats.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_clean_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/blackbox/test_ping.py -> build/bdist.linux-x86_64/wheel/breezy/tests/blackbox copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_registry.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_status.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_fetch_ghosts.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_trace.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_revert.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_progress.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_script.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_gpg.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_transport.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_tag.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_switch.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_generate_docs.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_annotate.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patch.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_merger.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_wsgi.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_lsprof.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_lock copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_lock/test_temporary_write_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_lock copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_lock/test_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_lock copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_lock/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_lock copying build/lib.linux-x86_64-cpython-310/breezy/tests/fake_command.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_config.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_mergeable.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_lazy_regex.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_transport.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_export.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/features.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_filters.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_strace.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_fixtures.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_forge.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_revisionspec.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/matchers.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_nonascii.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_identitymap.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_crash.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_permissions.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_setup.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_email_message.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_bad_files.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_decorators.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_revision.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_interbranch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch/test_fetch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interbranch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch/test_push.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interbranch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interbranch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch/test_pull.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interbranch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch/test_copy_content_into.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interbranch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interbranch/test_get.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interbranch copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_interrepository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interrepository/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interrepository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interrepository/test_interrepository.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interrepository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_interrepository/test_fetch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_interrepository copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_merge_directive.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_transport_log.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_subsume.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_timestamp.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_options.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_revisiontree.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_textmerge.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_dirty_tracker.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_location.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_memorybranch.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_plugins.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_scenarios.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test__walkdirs_win32.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_treeshape.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/file_utils.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_fetch.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_atomicfile.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_delta.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/stub_sftp.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_import_tariff.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_sampler.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_transactions.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_ssh_transport.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_help.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_version_info.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_bisect_multi.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_hooks.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_mutabletree.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/ui_testing.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_url_policy_open.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/script.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir_colo copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir_colo/test_unsupported.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir_colo copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir_colo/test_supported.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir_colo copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir_colo/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir_colo copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_treebuilder.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_whitebox.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/EncodingAdapter.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/http_server.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_pyutils.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_tsort.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_http_response.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_version.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/transport_util.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_osutils_encodings.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_textfile.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_i18n.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_cethread.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_log.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test__chunks_to_lines.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_bisect.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_conflicts.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_missing.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_lazy_import.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_rules.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_merge.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_library_state.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/https_server.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_ancestry.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_utextwrap.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_errors.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_win32utils.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_counted_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_reconfigure.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_shelf.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_selftest.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_checkout.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_update.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_cat.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_revert.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_missing.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_pull.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_branch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_init.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_merge.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_commit.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_push.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/commands/test_init_repository.py -> build/bdist.linux-x86_64/wheel/breezy/tests/commands copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_clean_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_upgrade_stacked.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_commit.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_graph.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/diff-5 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/mod-5 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/orig-5 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/orig -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/orig-2 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/mod-2 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/diff-2 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/diff-6 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/mod-6 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/orig-6 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/binary-after-normal.patch -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/mod -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/mod-3 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/binary.patch -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/diff-3 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/orig-3 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/orig-4 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/patchtext.patch -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/diff-4 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/diff -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/mod-4 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/orig-7 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/insert_top.patch -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/diff-7 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches_data/mod-7 -> build/bdist.linux-x86_64/wheel/breezy/tests/test_patches_data copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_shelf_ui.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_mail_client.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_multiwalker.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_http.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_rename_map.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/http_utils.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_memorytree.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_upgrade.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_ui.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_debug.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_features.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_branchbuilder.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/treeshape.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/fixtures.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_test_server.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_estimate_compressed_size.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_matchers.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_patches.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_mergetools.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_lru_cache.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_merge_core.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_msgeditor.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_diff.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/scenarios.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_commit_merge.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_upstream_import.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_https_ca_bundle.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_foreign_vcs copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_foreign_vcs/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_foreign_vcs copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_foreign_vcs/test_branch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_foreign_vcs copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_foreign_vcs/test_repository.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_foreign_vcs copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_smart_add.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_dotted_revno_to_revision_id.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_break_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_http.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_create_clone.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_get_rev_id.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_permissions.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_update.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_last_revision_info.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_sprout.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_pull.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_hooks.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_locking.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_reconcile.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_config.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_revision_id_to_revno.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_parent.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_revision_id_to_dotted_revno.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_get_revision_id_to_revno_map.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_stacking.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_branch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_create_checkout.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_iter_merge_sorted_revisions.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_push.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_tags.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_uncommit.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_commit.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_branch/test_check.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_branch copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_cache_utf8.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_all_revision_ids.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_get_rev_id_for_revno.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_add_signature_text.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_graph.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_commit_with_stacking.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_check.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_initialize.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test__make_parents_provider.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_add_inventory.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_default_stacking.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_get_record_stream.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_unlock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_break_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_fetch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository_reference/test_add_revision.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository_reference copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_chunk_writer.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_sftp_transport.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_branch.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_transform.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_locking.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_ids.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_iter_search_rules.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_get_root_id.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_test_trees.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_symlinks.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_export.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_path_content_summary.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_annotate_iter.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_get_symlink_target.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_archive.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_list_files.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_get_file_with_stat.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_get_file_mtime.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_revision_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_walkdirs.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_transform.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_tree/test_is_executable.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_tree copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_lockdir.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir/test_controldir.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir/test_format.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_controldir/test_push.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_controldir copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_info.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_lockable_files.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_unversion.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_executable.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_workingtree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_parents.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_break_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_pull.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_basis_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_mkdir.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_content_filters.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_nested_specifics.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_get_parent_ids.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_add_reference.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_rename_one.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_changes_from.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_is_control_filename.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_flush.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_set_root_id.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_readonly.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_add.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_views.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_canonical_path.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_get_file_mtime.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_commit.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_revision_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_symlinks.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_eol_conversion.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_basis_inventory.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_transform.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_smart_add.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_locking.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_check.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_paths2ids.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_move.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_put_file.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_shelf_manager.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_walkdirs.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_uncommit.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_inv.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_remove.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_is_ignored.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_annotate_iter.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_read_working_inventory.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_merge_from_branch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_workingtree/test_check_state.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_workingtree copying build/lib.linux-x86_64-cpython-310/breezy/tests/lock_helpers.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test__annotator.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_multiparent.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/ssl_certs copying build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs/server_with_pass.key -> build/bdist.linux-x86_64/wheel/breezy/tests/ssl_certs copying build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs/server_without_pass.key -> build/bdist.linux-x86_64/wheel/breezy/tests/ssl_certs copying build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs/server.crt -> build/bdist.linux-x86_64/wheel/breezy/tests/ssl_certs copying build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs/create_ssls.py -> build/bdist.linux-x86_64/wheel/breezy/tests/ssl_certs copying build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs/ca.crt -> build/bdist.linux-x86_64/wheel/breezy/tests/ssl_certs copying build/lib.linux-x86_64-cpython-310/breezy/tests/ssl_certs/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/ssl_certs copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_uncommit.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_commands.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_symbol_versioning.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_bugtracker.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_reconcile.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_controldir.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_intertree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree/test_file_content_matches.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_intertree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_intertree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree/test_compare.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_intertree copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_intertree/test_find_path.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_intertree copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_workspace.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_export_pot.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_foreign.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_grep.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_osutils.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_bedding.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_filter_tree.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test__known_graph.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_globbing.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_directory_service.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_smtp_connection.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_get_rev_id_for_revno.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_write_group.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_check.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_statistics.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_refresh_data.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_file_graph.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_pack.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_commit_builder.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_reconcile.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_fetch.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_has_revisions.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_get_parent_map.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_add_fallback_repository.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_break_lock.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_has_same_location.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_revision.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_repository.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_locking.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_repository/test_signatures.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_repository copying build/lib.linux-x86_64-cpython-310/breezy/tests/TestUtil.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_ignores.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/testui.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_eol_filters.py -> build/bdist.linux-x86_64/wheel/breezy/tests creating build/bdist.linux-x86_64/wheel/breezy/tests/per_uifactory copying build/lib.linux-x86_64-cpython-310/breezy/tests/per_uifactory/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/tests/per_uifactory copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_source.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_server.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_https_urllib.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/tests/test_extract.py -> build/bdist.linux-x86_64/wheel/breezy/tests copying build/lib.linux-x86_64-cpython-310/breezy/terminal.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/counted_lock.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/_known_graph_py.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/estimate_compressed_size.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/cmd_version_info.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/export_pot.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/controldir.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/smtp_connection.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/dirty_tracker.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/help_topics copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/help_topics creating build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/url-special-chars.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/diverged-branches.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/rules.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/glossary.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/eol.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/patterns.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/content-filters.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/configuration.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/missing-extensions.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/authentication.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/conflict-types.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/debug-flags.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/help_topics/en/log-formats.txt -> build/bdist.linux-x86_64/wheel/breezy/help_topics/en copying build/lib.linux-x86_64-cpython-310/breezy/multiwalker.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/utextwrap.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/mail_client.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/doc creating build/bdist.linux-x86_64/wheel/breezy/doc/api copying build/lib.linux-x86_64-cpython-310/breezy/doc/api/transport.txt -> build/bdist.linux-x86_64/wheel/breezy/doc/api copying build/lib.linux-x86_64-cpython-310/breezy/doc/api/branch.txt -> build/bdist.linux-x86_64/wheel/breezy/doc/api copying build/lib.linux-x86_64-cpython-310/breezy/doc/api/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/doc/api copying build/lib.linux-x86_64-cpython-310/breezy/doc/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/doc copying build/lib.linux-x86_64-cpython-310/breezy/conflicts.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/errors.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/builtins.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/msgeditor.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/bzr_distutils.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/upstream_import.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/lru_cache.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/version.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/cache_utf8.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/pyutils.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/check.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/bisect.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/help.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/bugtracker.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/i18n.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/commit.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/lazy_import.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/_annotator_py.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/shelf_ui.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/iterablefile.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/util copying build/lib.linux-x86_64-cpython-310/breezy/util/simplemapi.py -> build/bdist.linux-x86_64/wheel/breezy/util copying build/lib.linux-x86_64-cpython-310/breezy/util/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/util creating build/bdist.linux-x86_64/wheel/breezy/util/tests copying build/lib.linux-x86_64-cpython-310/breezy/util/tests/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/util/tests copying build/lib.linux-x86_64-cpython-310/breezy/lockable_files.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/push.py -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/_chunks_to_lines_pyx.cpython-310-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/breezy copying build/lib.linux-x86_64-cpython-310/breezy/add.py -> build/bdist.linux-x86_64/wheel/breezy creating build/bdist.linux-x86_64/wheel/breezy/version_info_formats copying build/lib.linux-x86_64-cpython-310/breezy/version_info_formats/format_python.py -> build/bdist.linux-x86_64/wheel/breezy/version_info_formats copying build/lib.linux-x86_64-cpython-310/breezy/version_info_formats/format_custom.py -> build/bdist.linux-x86_64/wheel/breezy/version_info_formats copying build/lib.linux-x86_64-cpython-310/breezy/version_info_formats/__init__.py -> build/bdist.linux-x86_64/wheel/breezy/version_info_formats copying build/lib.linux-x86_64-cpython-310/breezy/version_info_formats/format_rio.py -> build/bdist.linux-x86_64/wheel/breezy/version_info_formats copying build/lib.linux-x86_64-cpython-310/breezy/version_info_formats/format_yaml.py -> build/bdist.linux-x86_64/wheel/breezy/version_info_formats copying build/lib.linux-x86_64-cpython-310/breezy/reconfigure.py -> build/bdist.linux-x86_64/wheel/breezy running install_mo creating build/bdist.linux-x86_64/wheel/breezy-3.3.4.data creating build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/data running install_egg_info running egg_info writing breezy.egg-info/PKG-INFO writing dependency_links to breezy.egg-info/dependency_links.txt writing requirements to breezy.egg-info/requires.txt writing top-level names to breezy.egg-info/top_level.txt /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/command/sdist.py:121: SetuptoolsDeprecationWarning: Direct usage of `distutils` commands !! ******************************************************************************** It seems that you are using `distutils.command.build` to add new subcommands. Using `distutils` directly is considered deprecated, please use `setuptools.command.build`. By 2023-Dec-13, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://peps.python.org/pep-0632/ for details. ******************************************************************************** !! missing_cmds = set(build.get_sub_commands()) - _ORIGINAL_SUBCOMMANDS reading manifest file 'breezy.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'COPYING.txt' writing manifest file 'breezy.egg-info/SOURCES.txt' Copying breezy.egg-info to build/bdist.linux-x86_64/wheel/breezy-3.3.4-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts copying build/scripts-3.10/git-remote-bzr -> build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts copying build/scripts-3.10/bzr-receive-pack -> build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts copying build/scripts-3.10/brz -> build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts copying build/scripts-3.10/bzr-upload-pack -> build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts changing mode of build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts/git-remote-bzr to 755 changing mode of build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts/bzr-receive-pack to 755 changing mode of build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts/brz to 755 changing mode of build/bdist.linux-x86_64/wheel/breezy-3.3.4.data/scripts/bzr-upload-pack to 755 creating build/bdist.linux-x86_64/wheel/breezy-3.3.4.dist-info/WHEEL creating '/build/breezy-3.3.4/dist/.tmp-2uk0rr27/breezy-3.3.4-cp310-cp310-linux_x86_64.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'breezy/__init__.py' adding 'breezy/__main__.py' adding 'breezy/_annotator_py.py' adding 'breezy/_annotator_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/_chunks_to_lines_py.py' adding 'breezy/_chunks_to_lines_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/_known_graph_py.py' adding 'breezy/_known_graph_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/_readdir_py.py' adding 'breezy/_readdir_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/_termcolor.py' adding 'breezy/add.py' adding 'breezy/annotate.py' adding 'breezy/atomicfile.py' adding 'breezy/bedding.py' adding 'breezy/bisect.py' adding 'breezy/bisect_multi.py' adding 'breezy/branch.py' adding 'breezy/branchbuilder.py' adding 'breezy/breakin.py' adding 'breezy/bugtracker.py' adding 'breezy/builtins.py' adding 'breezy/bzr_distutils.py' adding 'breezy/cache_utf8.py' adding 'breezy/cethread.py' adding 'breezy/check.py' adding 'breezy/chunk_writer.py' adding 'breezy/clean_tree.py' adding 'breezy/cmd_test_script.py' adding 'breezy/cmd_version_info.py' adding 'breezy/cmdline.py' adding 'breezy/colordiff.py' adding 'breezy/commands.py' adding 'breezy/commit.py' adding 'breezy/commit_signature_commands.py' adding 'breezy/config.py' adding 'breezy/conflicts.py' adding 'breezy/controldir.py' adding 'breezy/counted_lock.py' adding 'breezy/crash.py' adding 'breezy/debug.py' adding 'breezy/decorators.py' adding 'breezy/delta.py' adding 'breezy/diff.py' adding 'breezy/directory_service.py' adding 'breezy/dirty_tracker.py' adding 'breezy/email_message.py' adding 'breezy/errors.py' adding 'breezy/estimate_compressed_size.py' adding 'breezy/export.py' adding 'breezy/export_pot.py' adding 'breezy/externalcommand.py' adding 'breezy/fetch_ghosts.py' adding 'breezy/fifo_cache.py' adding 'breezy/filter_tree.py' adding 'breezy/foreign.py' adding 'breezy/forge.py' adding 'breezy/globbing.py' adding 'breezy/gpg.py' adding 'breezy/graph.py' adding 'breezy/grep.py' adding 'breezy/help.py' adding 'breezy/hooks.py' adding 'breezy/i18n.py' adding 'breezy/identitymap.py' adding 'breezy/ignores.py' adding 'breezy/info.py' adding 'breezy/inter.py' adding 'breezy/iterablefile.py' adding 'breezy/lazy_import.py' adding 'breezy/lazy_regex.py' adding 'breezy/library_state.py' adding 'breezy/location.py' adding 'breezy/lock.py' adding 'breezy/lockable_files.py' adding 'breezy/lockdir.py' adding 'breezy/log.py' adding 'breezy/lru_cache.py' adding 'breezy/lsprof.py' adding 'breezy/mail_client.py' adding 'breezy/memorybranch.py' adding 'breezy/memorytree.py' adding 'breezy/merge.py' adding 'breezy/merge_directive.py' adding 'breezy/mergeable.py' adding 'breezy/mergetools.py' adding 'breezy/missing.py' adding 'breezy/msgeditor.py' adding 'breezy/multiparent.py' adding 'breezy/multiwalker.py' adding 'breezy/mutabletree.py' adding 'breezy/option.py' adding 'breezy/osutils.py' adding 'breezy/patch.py' adding 'breezy/patches.py' adding 'breezy/plugin.py' adding 'breezy/progress.py' adding 'breezy/push.py' adding 'breezy/py.typed' adding 'breezy/pyutils.py' adding 'breezy/reconcile.py' adding 'breezy/reconfigure.py' adding 'breezy/registry.py' adding 'breezy/rename_map.py' adding 'breezy/repository.py' adding 'breezy/revision.py' adding 'breezy/revisionspec.py' adding 'breezy/revisiontree.py' adding 'breezy/rules.py' adding 'breezy/send.py' adding 'breezy/shelf.py' adding 'breezy/shelf_ui.py' adding 'breezy/shellcomplete.py' adding 'breezy/smtp_connection.py' adding 'breezy/status.py' adding 'breezy/strace.py' adding 'breezy/switch.py' adding 'breezy/symbol_versioning.py' adding 'breezy/tag.py' adding 'breezy/terminal.py' adding 'breezy/textfile.py' adding 'breezy/textmerge.py' adding 'breezy/timestamp.py' adding 'breezy/trace.py' adding 'breezy/transactions.py' adding 'breezy/transform.py' adding 'breezy/tree.py' adding 'breezy/treebuilder.py' adding 'breezy/tsort.py' adding 'breezy/uncommit.py' adding 'breezy/upgrade.py' adding 'breezy/upstream_import.py' adding 'breezy/url_policy_open.py' adding 'breezy/urlutils.py' adding 'breezy/utextwrap.py' adding 'breezy/version.py' adding 'breezy/views.py' adding 'breezy/win32utils.py' adding 'breezy/workingtree.py' adding 'breezy/workspace.py' adding 'breezy/archive/__init__.py' adding 'breezy/archive/tar.py' adding 'breezy/archive/zip.py' adding 'breezy/bzr/__init__.py' adding 'breezy/bzr/_btree_serializer_py.py' adding 'breezy/bzr/_btree_serializer_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_chk_map_py.py' adding 'breezy/bzr/_chk_map_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_dirstate_helpers_py.py' adding 'breezy/bzr/_dirstate_helpers_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_groupcompress_py.py' adding 'breezy/bzr/_groupcompress_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_knit_load_data_py.py' adding 'breezy/bzr/_knit_load_data_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_rio_py.py' adding 'breezy/bzr/_rio_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_rio_rs.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_simple_set_pyx.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_static_tuple_c.cpython-310-x86_64-linux-gnu.so' adding 'breezy/bzr/_static_tuple_py.py' adding 'breezy/bzr/branch.py' adding 'breezy/bzr/btree_index.py' adding 'breezy/bzr/bzrdir.py' adding 'breezy/bzr/check.py' adding 'breezy/bzr/chk_map.py' adding 'breezy/bzr/chk_serializer.py' adding 'breezy/bzr/conflicts.py' adding 'breezy/bzr/debug_commands.py' adding 'breezy/bzr/dirstate.py' adding 'breezy/bzr/fetch.py' adding 'breezy/bzr/fullhistory.py' adding 'breezy/bzr/generate_ids.py' adding 'breezy/bzr/groupcompress.py' adding 'breezy/bzr/groupcompress_repo.py' adding 'breezy/bzr/hashcache.py' adding 'breezy/bzr/index.py' adding 'breezy/bzr/inventory.py' adding 'breezy/bzr/inventory_delta.py' adding 'breezy/bzr/inventorytree.py' adding 'breezy/bzr/knit.py' adding 'breezy/bzr/knitpack_repo.py' adding 'breezy/bzr/knitrepo.py' adding 'breezy/bzr/pack.py' adding 'breezy/bzr/pack_repo.py' adding 'breezy/bzr/reconcile.py' adding 'breezy/bzr/recordcounter.py' adding 'breezy/bzr/remote.py' adding 'breezy/bzr/repository.py' adding 'breezy/bzr/rio.py' adding 'breezy/bzr/serializer.py' adding 'breezy/bzr/static_tuple.py' adding 'breezy/bzr/tag.py' adding 'breezy/bzr/testament.py' adding 'breezy/bzr/textinv.py' adding 'breezy/bzr/transform.py' adding 'breezy/bzr/tuned_gzip.py' adding 'breezy/bzr/versionedfile.py' adding 'breezy/bzr/vf_repository.py' adding 'breezy/bzr/vf_search.py' adding 'breezy/bzr/weave.py' adding 'breezy/bzr/weavefile.py' adding 'breezy/bzr/workingtree.py' adding 'breezy/bzr/workingtree_3.py' adding 'breezy/bzr/workingtree_4.py' adding 'breezy/bzr/xml5.py' adding 'breezy/bzr/xml6.py' adding 'breezy/bzr/xml7.py' adding 'breezy/bzr/xml8.py' adding 'breezy/bzr/xml_serializer.py' adding 'breezy/bzr/bundle/__init__.py' adding 'breezy/bzr/bundle/apply_bundle.py' adding 'breezy/bzr/bundle/bundle_data.py' adding 'breezy/bzr/bundle/commands.py' adding 'breezy/bzr/bundle/serializer/__init__.py' adding 'breezy/bzr/bundle/serializer/v08.py' adding 'breezy/bzr/bundle/serializer/v09.py' adding 'breezy/bzr/bundle/serializer/v4.py' adding 'breezy/bzr/smart/__init__.py' adding 'breezy/bzr/smart/branch.py' adding 'breezy/bzr/smart/bzrdir.py' adding 'breezy/bzr/smart/client.py' adding 'breezy/bzr/smart/medium.py' adding 'breezy/bzr/smart/message.py' adding 'breezy/bzr/smart/packrepository.py' adding 'breezy/bzr/smart/ping.py' adding 'breezy/bzr/smart/protocol.py' adding 'breezy/bzr/smart/repository.py' adding 'breezy/bzr/smart/request.py' adding 'breezy/bzr/smart/server.py' adding 'breezy/bzr/smart/signals.py' adding 'breezy/bzr/smart/vfs.py' adding 'breezy/bzr/tests/__init__.py' adding 'breezy/bzr/tests/matchers.py' adding 'breezy/bzr/tests/per_pack_repository.py' adding 'breezy/bzr/tests/per_versionedfile.py' adding 'breezy/bzr/tests/test__btree_serializer.py' adding 'breezy/bzr/tests/test__chk_map.py' adding 'breezy/bzr/tests/test__dirstate_helpers.py' adding 'breezy/bzr/tests/test__groupcompress.py' adding 'breezy/bzr/tests/test__rio.py' adding 'breezy/bzr/tests/test__simple_set.py' adding 'breezy/bzr/tests/test__static_tuple.py' adding 'breezy/bzr/tests/test_btree_index.py' adding 'breezy/bzr/tests/test_bundle.py' adding 'breezy/bzr/tests/test_bzrdir.py' adding 'breezy/bzr/tests/test_chk_map.py' adding 'breezy/bzr/tests/test_chk_serializer.py' adding 'breezy/bzr/tests/test_conflicts.py' adding 'breezy/bzr/tests/test_dirstate.py' adding 'breezy/bzr/tests/test_generate_ids.py' adding 'breezy/bzr/tests/test_groupcompress.py' adding 'breezy/bzr/tests/test_hashcache.py' adding 'breezy/bzr/tests/test_index.py' adding 'breezy/bzr/tests/test_inv.py' adding 'breezy/bzr/tests/test_inventory_delta.py' adding 'breezy/bzr/tests/test_knit.py' adding 'breezy/bzr/tests/test_matchers.py' adding 'breezy/bzr/tests/test_pack.py' adding 'breezy/bzr/tests/test_read_bundle.py' adding 'breezy/bzr/tests/test_remote.py' adding 'breezy/bzr/tests/test_repository.py' adding 'breezy/bzr/tests/test_rio.py' adding 'breezy/bzr/tests/test_serializer.py' adding 'breezy/bzr/tests/test_smart.py' adding 'breezy/bzr/tests/test_smart_request.py' adding 'breezy/bzr/tests/test_smart_signals.py' adding 'breezy/bzr/tests/test_smart_transport.py' adding 'breezy/bzr/tests/test_tag.py' adding 'breezy/bzr/tests/test_testament.py' adding 'breezy/bzr/tests/test_transform.py' adding 'breezy/bzr/tests/test_tuned_gzip.py' adding 'breezy/bzr/tests/test_versionedfile.py' adding 'breezy/bzr/tests/test_vf_search.py' adding 'breezy/bzr/tests/test_vfs_ratchet.py' adding 'breezy/bzr/tests/test_weave.py' adding 'breezy/bzr/tests/test_workingtree.py' adding 'breezy/bzr/tests/test_workingtree_4.py' adding 'breezy/bzr/tests/test_xml.py' adding 'breezy/bzr/tests/blackbox/__init__.py' adding 'breezy/bzr/tests/blackbox/test_dump_btree.py' adding 'breezy/bzr/tests/per_bzrdir/__init__.py' adding 'breezy/bzr/tests/per_bzrdir/test_bzrdir.py' adding 'breezy/bzr/tests/per_inventory/__init__.py' adding 'breezy/bzr/tests/per_inventory/basics.py' adding 'breezy/bzr/tests/per_repository_chk/__init__.py' adding 'breezy/bzr/tests/per_repository_chk/test_supported.py' adding 'breezy/bzr/tests/per_repository_chk/test_unsupported.py' adding 'breezy/bzr/tests/per_repository_vf/__init__.py' adding 'breezy/bzr/tests/per_repository_vf/helpers.py' adding 'breezy/bzr/tests/per_repository_vf/test__generate_text_key_index.py' adding 'breezy/bzr/tests/per_repository_vf/test_add_inventory_by_delta.py' adding 'breezy/bzr/tests/per_repository_vf/test_check.py' adding 'breezy/bzr/tests/per_repository_vf/test_check_reconcile.py' adding 'breezy/bzr/tests/per_repository_vf/test_fetch.py' adding 'breezy/bzr/tests/per_repository_vf/test_fileid_involved.py' adding 'breezy/bzr/tests/per_repository_vf/test_find_text_key_references.py' adding 'breezy/bzr/tests/per_repository_vf/test_merge_directive.py' adding 'breezy/bzr/tests/per_repository_vf/test_reconcile.py' adding 'breezy/bzr/tests/per_repository_vf/test_refresh_data.py' adding 'breezy/bzr/tests/per_repository_vf/test_repository.py' adding 'breezy/bzr/tests/per_repository_vf/test_write_group.py' adding 'breezy/doc/__init__.py' adding 'breezy/doc/api/__init__.py' adding 'breezy/doc/api/branch.txt' adding 'breezy/doc/api/transport.txt' adding 'breezy/doc_generate/__init__.py' adding 'breezy/doc_generate/autodoc_bash_completion.py' adding 'breezy/doc_generate/autodoc_man.py' adding 'breezy/doc_generate/autodoc_rstx.py' adding 'breezy/doc_generate/conf.py' adding 'breezy/filters/__init__.py' adding 'breezy/filters/eol.py' adding 'breezy/git/__init__.py' adding 'breezy/git/annotate.py' adding 'breezy/git/branch.py' adding 'breezy/git/cache.py' adding 'breezy/git/commands.py' adding 'breezy/git/commit.py' adding 'breezy/git/config.py' adding 'breezy/git/dir.py' adding 'breezy/git/directory.py' adding 'breezy/git/errors.py' adding 'breezy/git/fetch.py' adding 'breezy/git/filegraph.py' adding 'breezy/git/git_remote_helper.py' adding 'breezy/git/help.py' adding 'breezy/git/hg.py' adding 'breezy/git/interrepo.py' adding 'breezy/git/mapping.py' adding 'breezy/git/memorytree.py' adding 'breezy/git/object_store.py' adding 'breezy/git/pristine_tar.py' adding 'breezy/git/push.py' adding 'breezy/git/refs.py' adding 'breezy/git/remote.py' adding 'breezy/git/repository.py' adding 'breezy/git/revspec.py' adding 'breezy/git/roundtrip.py' adding 'breezy/git/send.py' adding 'breezy/git/server.py' adding 'breezy/git/transform.py' adding 'breezy/git/transportgit.py' adding 'breezy/git/tree.py' adding 'breezy/git/unpeel_map.py' adding 'breezy/git/urls.py' adding 'breezy/git/workingtree.py' adding 'breezy/git/tests/__init__.py' adding 'breezy/git/tests/test_blackbox.py' adding 'breezy/git/tests/test_branch.py' adding 'breezy/git/tests/test_builder.py' adding 'breezy/git/tests/test_cache.py' adding 'breezy/git/tests/test_dir.py' adding 'breezy/git/tests/test_fetch.py' adding 'breezy/git/tests/test_git_remote_helper.py' adding 'breezy/git/tests/test_mapping.py' adding 'breezy/git/tests/test_memorytree.py' adding 'breezy/git/tests/test_object_store.py' adding 'breezy/git/tests/test_pristine_tar.py' adding 'breezy/git/tests/test_push.py' adding 'breezy/git/tests/test_refs.py' adding 'breezy/git/tests/test_remote.py' adding 'breezy/git/tests/test_repository.py' adding 'breezy/git/tests/test_revspec.py' adding 'breezy/git/tests/test_roundtrip.py' adding 'breezy/git/tests/test_server.py' adding 'breezy/git/tests/test_transform.py' adding 'breezy/git/tests/test_transportgit.py' adding 'breezy/git/tests/test_tree.py' adding 'breezy/git/tests/test_unpeel_map.py' adding 'breezy/git/tests/test_urls.py' adding 'breezy/git/tests/test_workingtree.py' adding 'breezy/help_topics/__init__.py' adding 'breezy/help_topics/en/authentication.txt' adding 'breezy/help_topics/en/configuration.txt' adding 'breezy/help_topics/en/conflict-types.txt' adding 'breezy/help_topics/en/content-filters.txt' adding 'breezy/help_topics/en/debug-flags.txt' adding 'breezy/help_topics/en/diverged-branches.txt' adding 'breezy/help_topics/en/eol.txt' adding 'breezy/help_topics/en/glossary.txt' adding 'breezy/help_topics/en/log-formats.txt' adding 'breezy/help_topics/en/missing-extensions.txt' adding 'breezy/help_topics/en/patterns.txt' adding 'breezy/help_topics/en/rules.txt' adding 'breezy/help_topics/en/url-special-chars.txt' adding 'breezy/plugins/__init__.py' adding 'breezy/plugins/bash_completion/__init__.py' adding 'breezy/plugins/bash_completion/bashcomp.py' adding 'breezy/plugins/bash_completion/tests/__init__.py' adding 'breezy/plugins/bash_completion/tests/test_bashcomp.py' adding 'breezy/plugins/changelog_merge/__init__.py' adding 'breezy/plugins/changelog_merge/changelog_merge.py' adding 'breezy/plugins/changelog_merge/tests/__init__.py' adding 'breezy/plugins/changelog_merge/tests/test_changelog_merge.py' adding 'breezy/plugins/commitfromnews/__init__.py' adding 'breezy/plugins/commitfromnews/committemplate.py' adding 'breezy/plugins/commitfromnews/tests/__init__.py' adding 'breezy/plugins/commitfromnews/tests/test_committemplate.py' adding 'breezy/plugins/commitfromnews/tests/test_msgeditor.py' adding 'breezy/plugins/cvs/__init__.py' adding 'breezy/plugins/darcs/__init__.py' adding 'breezy/plugins/email/__init__.py' adding 'breezy/plugins/email/emailer.py' adding 'breezy/plugins/email/tests/__init__.py' adding 'breezy/plugins/email/tests/testemail.py' adding 'breezy/plugins/fastimport/__init__.py' adding 'breezy/plugins/fastimport/branch_mapper.py' adding 'breezy/plugins/fastimport/branch_updater.py' adding 'breezy/plugins/fastimport/bzr_commit_handler.py' adding 'breezy/plugins/fastimport/cache_manager.py' adding 'breezy/plugins/fastimport/cmds.py' adding 'breezy/plugins/fastimport/exporter.py' adding 'breezy/plugins/fastimport/helpers.py' adding 'breezy/plugins/fastimport/idmapfile.py' adding 'breezy/plugins/fastimport/marks_file.py' adding 'breezy/plugins/fastimport/revision_store.py' adding 'breezy/plugins/fastimport/user_mapper.py' adding 'breezy/plugins/fastimport/processors/__init__.py' adding 'breezy/plugins/fastimport/processors/generic_processor.py' adding 'breezy/plugins/fastimport/tests/__init__.py' adding 'breezy/plugins/fastimport/tests/test_branch_mapper.py' adding 'breezy/plugins/fastimport/tests/test_commands.py' adding 'breezy/plugins/fastimport/tests/test_exporter.py' adding 'breezy/plugins/fastimport/tests/test_generic_processor.py' adding 'breezy/plugins/fastimport/tests/test_head_tracking.py' adding 'breezy/plugins/fastimport/tests/test_marks_file.py' adding 'breezy/plugins/fastimport/tests/test_revision_store.py' adding 'breezy/plugins/flake8/__init__.py' adding 'breezy/plugins/fossil/__init__.py' adding 'breezy/plugins/github/__init__.py' adding 'breezy/plugins/github/cmds.py' adding 'breezy/plugins/github/forge.py' adding 'breezy/plugins/github/tests/__init__.py' adding 'breezy/plugins/github/tests/test_forge.py' adding 'breezy/plugins/gitlab/__init__.py' adding 'breezy/plugins/gitlab/cmds.py' adding 'breezy/plugins/gitlab/forge.py' adding 'breezy/plugins/gitlab/tests/__init__.py' adding 'breezy/plugins/gitlab/tests/test_forge.py' adding 'breezy/plugins/hg/__init__.py' adding 'breezy/plugins/launchpad/__init__.py' adding 'breezy/plugins/launchpad/account.py' adding 'breezy/plugins/launchpad/cmds.py' adding 'breezy/plugins/launchpad/forge.py' adding 'breezy/plugins/launchpad/lp_api.py' adding 'breezy/plugins/launchpad/lp_directory.py' adding 'breezy/plugins/launchpad/test_account.py' adding 'breezy/plugins/launchpad/test_lp_api.py' adding 'breezy/plugins/launchpad/test_lp_directory.py' adding 'breezy/plugins/launchpad/test_lp_login.py' adding 'breezy/plugins/launchpad/uris.py' adding 'breezy/plugins/mtn/__init__.py' adding 'breezy/plugins/netrc_credential_store/__init__.py' adding 'breezy/plugins/netrc_credential_store/tests/__init__.py' adding 'breezy/plugins/netrc_credential_store/tests/test_netrc.py' adding 'breezy/plugins/news_merge/__init__.py' adding 'breezy/plugins/news_merge/news_merge.py' adding 'breezy/plugins/news_merge/parser.py' adding 'breezy/plugins/news_merge/tests/__init__.py' adding 'breezy/plugins/news_merge/tests/test_news_merge.py' adding 'breezy/plugins/po_merge/__init__.py' adding 'breezy/plugins/po_merge/po_merge.py' adding 'breezy/plugins/po_merge/tests/__init__.py' adding 'breezy/plugins/po_merge/tests/test_po_merge.py' adding 'breezy/plugins/propose/__init__.py' adding 'breezy/plugins/propose/cmds.py' adding 'breezy/plugins/propose/tests/__init__.py' adding 'breezy/plugins/pypi/__init__.py' adding 'breezy/plugins/pypi/directory.py' adding 'breezy/plugins/quilt/__init__.py' adding 'breezy/plugins/quilt/merge.py' adding 'breezy/plugins/quilt/quilt.py' adding 'breezy/plugins/quilt/wrapper.py' adding 'breezy/plugins/quilt/tests/__init__.py' adding 'breezy/plugins/quilt/tests/test_merge.py' adding 'breezy/plugins/quilt/tests/test_wrapper.py' adding 'breezy/plugins/repodebug/__init__.py' adding 'breezy/plugins/repodebug/check_chk.py' adding 'breezy/plugins/repodebug/chk_used_by.py' adding 'breezy/plugins/repodebug/fetch_all_records.py' adding 'breezy/plugins/repodebug/file_refs.py' adding 'breezy/plugins/repodebug/missing_keys_for_stacking_fixer.py' adding 'breezy/plugins/repodebug/repo_has_key.py' adding 'breezy/plugins/repodebug/repo_keys.py' adding 'breezy/plugins/repodebug/tests/__init__.py' adding 'breezy/plugins/rewrite/__init__.py' adding 'breezy/plugins/rewrite/commands.py' adding 'breezy/plugins/rewrite/maptree.py' adding 'breezy/plugins/rewrite/pseudonyms.py' adding 'breezy/plugins/rewrite/rebase.py' adding 'breezy/plugins/rewrite/upgrade.py' adding 'breezy/plugins/rewrite/tests/__init__.py' adding 'breezy/plugins/rewrite/tests/test_blackbox.py' adding 'breezy/plugins/rewrite/tests/test_maptree.py' adding 'breezy/plugins/rewrite/tests/test_pseudonyms.py' adding 'breezy/plugins/rewrite/tests/test_rebase.py' adding 'breezy/plugins/rewrite/tests/test_upgrade.py' adding 'breezy/plugins/stats/__init__.py' adding 'breezy/plugins/stats/classify.py' adding 'breezy/plugins/stats/cmds.py' adding 'breezy/plugins/stats/test_blackbox.py' adding 'breezy/plugins/stats/test_classify.py' adding 'breezy/plugins/stats/test_stats.py' adding 'breezy/plugins/svn/__init__.py' adding 'breezy/plugins/svn/revspec.py' adding 'breezy/plugins/upload/__init__.py' adding 'breezy/plugins/upload/cmds.py' adding 'breezy/plugins/upload/tests/__init__.py' adding 'breezy/plugins/upload/tests/test_auto_upload_hook.py' adding 'breezy/plugins/upload/tests/test_upload.py' adding 'breezy/plugins/weave_fmt/__init__.py' adding 'breezy/plugins/weave_fmt/branch.py' adding 'breezy/plugins/weave_fmt/bzrdir.py' adding 'breezy/plugins/weave_fmt/repository.py' adding 'breezy/plugins/weave_fmt/test_bzrdir.py' adding 'breezy/plugins/weave_fmt/test_repository.py' adding 'breezy/plugins/weave_fmt/test_store.py' adding 'breezy/plugins/weave_fmt/test_workingtree.py' adding 'breezy/plugins/weave_fmt/workingtree.py' adding 'breezy/plugins/weave_fmt/xml4.py' adding 'breezy/plugins/weave_fmt/store/__init__.py' adding 'breezy/plugins/weave_fmt/store/text.py' adding 'breezy/plugins/weave_fmt/store/versioned.py' adding 'breezy/plugins/webdav/__init__.py' adding 'breezy/plugins/webdav/webdav.py' adding 'breezy/plugins/webdav/tests/__init__.py' adding 'breezy/plugins/webdav/tests/dav_server.py' adding 'breezy/plugins/webdav/tests/test_webdav.py' adding 'breezy/plugins/zsh_completion/__init__.py' adding 'breezy/plugins/zsh_completion/zshcomp.py' adding 'breezy/plugins/zsh_completion/tests/__init__.py' adding 'breezy/plugins/zsh_completion/tests/test_zshcomp.py' adding 'breezy/tests/EncodingAdapter.py' adding 'breezy/tests/TestUtil.py' adding 'breezy/tests/__init__.py' adding 'breezy/tests/fake_command.py' adding 'breezy/tests/features.py' adding 'breezy/tests/file_utils.py' adding 'breezy/tests/fixtures.py' adding 'breezy/tests/http_server.py' adding 'breezy/tests/http_utils.py' adding 'breezy/tests/https_server.py' adding 'breezy/tests/lock_helpers.py' adding 'breezy/tests/matchers.py' adding 'breezy/tests/per_merger.py' adding 'breezy/tests/per_transport.py' adding 'breezy/tests/scenarios.py' adding 'breezy/tests/script.py' adding 'breezy/tests/stub_sftp.py' adding 'breezy/tests/test__annotator.py' adding 'breezy/tests/test__chunks_to_lines.py' adding 'breezy/tests/test__known_graph.py' adding 'breezy/tests/test__walkdirs_win32.py' adding 'breezy/tests/test_ancestry.py' adding 'breezy/tests/test_annotate.py' adding 'breezy/tests/test_atomicfile.py' adding 'breezy/tests/test_bad_files.py' adding 'breezy/tests/test_bedding.py' adding 'breezy/tests/test_bisect.py' adding 'breezy/tests/test_bisect_multi.py' adding 'breezy/tests/test_branch.py' adding 'breezy/tests/test_branchbuilder.py' adding 'breezy/tests/test_bugtracker.py' adding 'breezy/tests/test_cache_utf8.py' adding 'breezy/tests/test_cethread.py' adding 'breezy/tests/test_chunk_writer.py' adding 'breezy/tests/test_clean_tree.py' adding 'breezy/tests/test_cmdline.py' adding 'breezy/tests/test_commands.py' adding 'breezy/tests/test_commit.py' adding 'breezy/tests/test_commit_merge.py' adding 'breezy/tests/test_config.py' adding 'breezy/tests/test_conflicts.py' adding 'breezy/tests/test_controldir.py' adding 'breezy/tests/test_counted_lock.py' adding 'breezy/tests/test_crash.py' adding 'breezy/tests/test_debug.py' adding 'breezy/tests/test_decorators.py' adding 'breezy/tests/test_delta.py' adding 'breezy/tests/test_diff.py' adding 'breezy/tests/test_directory_service.py' adding 'breezy/tests/test_dirty_tracker.py' adding 'breezy/tests/test_email_message.py' adding 'breezy/tests/test_eol_filters.py' adding 'breezy/tests/test_errors.py' adding 'breezy/tests/test_estimate_compressed_size.py' adding 'breezy/tests/test_export.py' adding 'breezy/tests/test_export_pot.py' adding 'breezy/tests/test_extract.py' adding 'breezy/tests/test_features.py' adding 'breezy/tests/test_fetch.py' adding 'breezy/tests/test_fetch_ghosts.py' adding 'breezy/tests/test_fifo_cache.py' adding 'breezy/tests/test_filter_tree.py' adding 'breezy/tests/test_filters.py' adding 'breezy/tests/test_fixtures.py' adding 'breezy/tests/test_foreign.py' adding 'breezy/tests/test_forge.py' adding 'breezy/tests/test_generate_docs.py' adding 'breezy/tests/test_globbing.py' adding 'breezy/tests/test_gpg.py' adding 'breezy/tests/test_graph.py' adding 'breezy/tests/test_grep.py' adding 'breezy/tests/test_help.py' adding 'breezy/tests/test_hooks.py' adding 'breezy/tests/test_http.py' adding 'breezy/tests/test_http_response.py' adding 'breezy/tests/test_https_ca_bundle.py' adding 'breezy/tests/test_https_urllib.py' adding 'breezy/tests/test_i18n.py' adding 'breezy/tests/test_identitymap.py' adding 'breezy/tests/test_ignores.py' adding 'breezy/tests/test_import_tariff.py' adding 'breezy/tests/test_info.py' adding 'breezy/tests/test_lazy_import.py' adding 'breezy/tests/test_lazy_regex.py' adding 'breezy/tests/test_library_state.py' adding 'breezy/tests/test_location.py' adding 'breezy/tests/test_lock.py' adding 'breezy/tests/test_lockable_files.py' adding 'breezy/tests/test_lockdir.py' adding 'breezy/tests/test_log.py' adding 'breezy/tests/test_lru_cache.py' adding 'breezy/tests/test_lsprof.py' adding 'breezy/tests/test_mail_client.py' adding 'breezy/tests/test_matchers.py' adding 'breezy/tests/test_memorybranch.py' adding 'breezy/tests/test_memorytree.py' adding 'breezy/tests/test_merge.py' adding 'breezy/tests/test_merge_core.py' adding 'breezy/tests/test_merge_directive.py' adding 'breezy/tests/test_mergeable.py' adding 'breezy/tests/test_mergetools.py' adding 'breezy/tests/test_missing.py' adding 'breezy/tests/test_msgeditor.py' adding 'breezy/tests/test_multiparent.py' adding 'breezy/tests/test_multiwalker.py' adding 'breezy/tests/test_mutabletree.py' adding 'breezy/tests/test_nonascii.py' adding 'breezy/tests/test_options.py' adding 'breezy/tests/test_osutils.py' adding 'breezy/tests/test_osutils_encodings.py' adding 'breezy/tests/test_patch.py' adding 'breezy/tests/test_patches.py' adding 'breezy/tests/test_permissions.py' adding 'breezy/tests/test_plugins.py' adding 'breezy/tests/test_progress.py' adding 'breezy/tests/test_pyutils.py' adding 'breezy/tests/test_reconcile.py' adding 'breezy/tests/test_reconfigure.py' adding 'breezy/tests/test_registry.py' adding 'breezy/tests/test_rename_map.py' adding 'breezy/tests/test_revert.py' adding 'breezy/tests/test_revision.py' adding 'breezy/tests/test_revisionspec.py' adding 'breezy/tests/test_revisiontree.py' adding 'breezy/tests/test_rules.py' adding 'breezy/tests/test_sampler.py' adding 'breezy/tests/test_scenarios.py' adding 'breezy/tests/test_script.py' adding 'breezy/tests/test_selftest.py' adding 'breezy/tests/test_server.py' adding 'breezy/tests/test_setup.py' adding 'breezy/tests/test_sftp_transport.py' adding 'breezy/tests/test_shelf.py' adding 'breezy/tests/test_shelf_ui.py' adding 'breezy/tests/test_smart_add.py' adding 'breezy/tests/test_smtp_connection.py' adding 'breezy/tests/test_source.py' adding 'breezy/tests/test_ssh_transport.py' adding 'breezy/tests/test_status.py' adding 'breezy/tests/test_strace.py' adding 'breezy/tests/test_subsume.py' adding 'breezy/tests/test_switch.py' adding 'breezy/tests/test_symbol_versioning.py' adding 'breezy/tests/test_tag.py' adding 'breezy/tests/test_test_server.py' adding 'breezy/tests/test_textfile.py' adding 'breezy/tests/test_textmerge.py' adding 'breezy/tests/test_timestamp.py' adding 'breezy/tests/test_trace.py' adding 'breezy/tests/test_transactions.py' adding 'breezy/tests/test_transform.py' adding 'breezy/tests/test_transport.py' adding 'breezy/tests/test_transport_log.py' adding 'breezy/tests/test_tree.py' adding 'breezy/tests/test_treebuilder.py' adding 'breezy/tests/test_treeshape.py' adding 'breezy/tests/test_tsort.py' adding 'breezy/tests/test_ui.py' adding 'breezy/tests/test_uncommit.py' adding 'breezy/tests/test_upgrade.py' adding 'breezy/tests/test_upgrade_stacked.py' adding 'breezy/tests/test_upstream_import.py' adding 'breezy/tests/test_url_policy_open.py' adding 'breezy/tests/test_urlutils.py' adding 'breezy/tests/test_utextwrap.py' adding 'breezy/tests/test_version.py' adding 'breezy/tests/test_version_info.py' adding 'breezy/tests/test_views.py' adding 'breezy/tests/test_whitebox.py' adding 'breezy/tests/test_win32utils.py' adding 'breezy/tests/test_workingtree.py' adding 'breezy/tests/test_workspace.py' adding 'breezy/tests/test_wsgi.py' adding 'breezy/tests/testui.py' adding 'breezy/tests/transport_util.py' adding 'breezy/tests/treeshape.py' adding 'breezy/tests/ui_testing.py' adding 'breezy/tests/blackbox/__init__.py' adding 'breezy/tests/blackbox/test_add.py' adding 'breezy/tests/blackbox/test_added.py' adding 'breezy/tests/blackbox/test_alias.py' adding 'breezy/tests/blackbox/test_aliases.py' adding 'breezy/tests/blackbox/test_ancestry.py' adding 'breezy/tests/blackbox/test_annotate.py' adding 'breezy/tests/blackbox/test_big_file.py' adding 'breezy/tests/blackbox/test_bisect.py' adding 'breezy/tests/blackbox/test_bound_branches.py' adding 'breezy/tests/blackbox/test_branch.py' adding 'breezy/tests/blackbox/test_branches.py' adding 'breezy/tests/blackbox/test_break_lock.py' adding 'breezy/tests/blackbox/test_bundle_info.py' adding 'breezy/tests/blackbox/test_cat.py' adding 'breezy/tests/blackbox/test_cat_revision.py' adding 'breezy/tests/blackbox/test_check.py' adding 'breezy/tests/blackbox/test_checkout.py' adding 'breezy/tests/blackbox/test_clean_tree.py' adding 'breezy/tests/blackbox/test_clone.py' adding 'breezy/tests/blackbox/test_command_encoding.py' adding 'breezy/tests/blackbox/test_commit.py' adding 'breezy/tests/blackbox/test_config.py' adding 'breezy/tests/blackbox/test_conflicts.py' adding 'breezy/tests/blackbox/test_cp.py' adding 'breezy/tests/blackbox/test_debug.py' adding 'breezy/tests/blackbox/test_deleted.py' adding 'breezy/tests/blackbox/test_diff.py' adding 'breezy/tests/blackbox/test_exceptions.py' adding 'breezy/tests/blackbox/test_export.py' adding 'breezy/tests/blackbox/test_export_pot.py' adding 'breezy/tests/blackbox/test_fetch_ghosts.py' adding 'breezy/tests/blackbox/test_filesystem_cicp.py' adding 'breezy/tests/blackbox/test_filtered_view_ops.py' adding 'breezy/tests/blackbox/test_find_merge_base.py' adding 'breezy/tests/blackbox/test_help.py' adding 'breezy/tests/blackbox/test_hooks.py' adding 'breezy/tests/blackbox/test_ignore.py' adding 'breezy/tests/blackbox/test_ignored.py' adding 'breezy/tests/blackbox/test_import.py' adding 'breezy/tests/blackbox/test_info.py' adding 'breezy/tests/blackbox/test_init.py' adding 'breezy/tests/blackbox/test_inventory.py' adding 'breezy/tests/blackbox/test_join.py' adding 'breezy/tests/blackbox/test_link_tree.py' adding 'breezy/tests/blackbox/test_locale.py' adding 'breezy/tests/blackbox/test_log.py' adding 'breezy/tests/blackbox/test_logformats.py' adding 'breezy/tests/blackbox/test_lookup_revision.py' adding 'breezy/tests/blackbox/test_ls.py' adding 'breezy/tests/blackbox/test_lsprof.py' adding 'breezy/tests/blackbox/test_merge.py' adding 'breezy/tests/blackbox/test_merge_directive.py' adding 'breezy/tests/blackbox/test_missing.py' adding 'breezy/tests/blackbox/test_mkdir.py' adding 'breezy/tests/blackbox/test_modified.py' adding 'breezy/tests/blackbox/test_mv.py' adding 'breezy/tests/blackbox/test_nick.py' adding 'breezy/tests/blackbox/test_non_ascii.py' adding 'breezy/tests/blackbox/test_outside_wt.py' adding 'breezy/tests/blackbox/test_pack.py' adding 'breezy/tests/blackbox/test_patch.py' adding 'breezy/tests/blackbox/test_ping.py' adding 'breezy/tests/blackbox/test_plugins.py' adding 'breezy/tests/blackbox/test_pull.py' adding 'breezy/tests/blackbox/test_push.py' adding 'breezy/tests/blackbox/test_re_sign.py' adding 'breezy/tests/blackbox/test_reconcile.py' adding 'breezy/tests/blackbox/test_reconfigure.py' adding 'breezy/tests/blackbox/test_reference.py' adding 'breezy/tests/blackbox/test_remember_option.py' adding 'breezy/tests/blackbox/test_remerge.py' adding 'breezy/tests/blackbox/test_remove.py' adding 'breezy/tests/blackbox/test_remove_tree.py' adding 'breezy/tests/blackbox/test_repair_workingtree.py' adding 'breezy/tests/blackbox/test_resolve.py' adding 'breezy/tests/blackbox/test_resolve_location.py' adding 'breezy/tests/blackbox/test_revert.py' adding 'breezy/tests/blackbox/test_revision_history.py' adding 'breezy/tests/blackbox/test_revision_info.py' adding 'breezy/tests/blackbox/test_revno.py' adding 'breezy/tests/blackbox/test_rmbranch.py' adding 'breezy/tests/blackbox/test_script.py' adding 'breezy/tests/blackbox/test_selftest.py' adding 'breezy/tests/blackbox/test_send.py' adding 'breezy/tests/blackbox/test_serve.py' adding 'breezy/tests/blackbox/test_shared_repository.py' adding 'breezy/tests/blackbox/test_shell_complete.py' adding 'breezy/tests/blackbox/test_shelve.py' adding 'breezy/tests/blackbox/test_sign_my_commits.py' adding 'breezy/tests/blackbox/test_split.py' adding 'breezy/tests/blackbox/test_status.py' adding 'breezy/tests/blackbox/test_switch.py' adding 'breezy/tests/blackbox/test_tags.py' adding 'breezy/tests/blackbox/test_testament.py' adding 'breezy/tests/blackbox/test_too_much.py' adding 'breezy/tests/blackbox/test_uncommit.py' adding 'breezy/tests/blackbox/test_unknowns.py' adding 'breezy/tests/blackbox/test_update.py' adding 'breezy/tests/blackbox/test_upgrade.py' adding 'breezy/tests/blackbox/test_verify_signatures.py' adding 'breezy/tests/blackbox/test_version.py' adding 'breezy/tests/blackbox/test_version_info.py' adding 'breezy/tests/blackbox/test_versioning.py' adding 'breezy/tests/blackbox/test_view.py' adding 'breezy/tests/blackbox/test_whoami.py' adding 'breezy/tests/commands/__init__.py' adding 'breezy/tests/commands/test_branch.py' adding 'breezy/tests/commands/test_cat.py' adding 'breezy/tests/commands/test_checkout.py' adding 'breezy/tests/commands/test_commit.py' adding 'breezy/tests/commands/test_init.py' adding 'breezy/tests/commands/test_init_repository.py' adding 'breezy/tests/commands/test_merge.py' adding 'breezy/tests/commands/test_missing.py' adding 'breezy/tests/commands/test_pull.py' adding 'breezy/tests/commands/test_push.py' adding 'breezy/tests/commands/test_revert.py' adding 'breezy/tests/commands/test_update.py' adding 'breezy/tests/per_branch/__init__.py' adding 'breezy/tests/per_branch/test_branch.py' adding 'breezy/tests/per_branch/test_break_lock.py' adding 'breezy/tests/per_branch/test_check.py' adding 'breezy/tests/per_branch/test_commit.py' adding 'breezy/tests/per_branch/test_config.py' adding 'breezy/tests/per_branch/test_create_checkout.py' adding 'breezy/tests/per_branch/test_create_clone.py' adding 'breezy/tests/per_branch/test_dotted_revno_to_revision_id.py' adding 'breezy/tests/per_branch/test_get_rev_id.py' adding 'breezy/tests/per_branch/test_get_revision_id_to_revno_map.py' adding 'breezy/tests/per_branch/test_hooks.py' adding 'breezy/tests/per_branch/test_http.py' adding 'breezy/tests/per_branch/test_iter_merge_sorted_revisions.py' adding 'breezy/tests/per_branch/test_last_revision_info.py' adding 'breezy/tests/per_branch/test_locking.py' adding 'breezy/tests/per_branch/test_parent.py' adding 'breezy/tests/per_branch/test_permissions.py' adding 'breezy/tests/per_branch/test_pull.py' adding 'breezy/tests/per_branch/test_push.py' adding 'breezy/tests/per_branch/test_reconcile.py' adding 'breezy/tests/per_branch/test_revision_id_to_dotted_revno.py' adding 'breezy/tests/per_branch/test_revision_id_to_revno.py' adding 'breezy/tests/per_branch/test_sprout.py' adding 'breezy/tests/per_branch/test_stacking.py' adding 'breezy/tests/per_branch/test_tags.py' adding 'breezy/tests/per_branch/test_uncommit.py' adding 'breezy/tests/per_branch/test_update.py' adding 'breezy/tests/per_controldir/__init__.py' adding 'breezy/tests/per_controldir/test_controldir.py' adding 'breezy/tests/per_controldir/test_format.py' adding 'breezy/tests/per_controldir/test_push.py' adding 'breezy/tests/per_controldir_colo/__init__.py' adding 'breezy/tests/per_controldir_colo/test_supported.py' adding 'breezy/tests/per_controldir_colo/test_unsupported.py' adding 'breezy/tests/per_foreign_vcs/__init__.py' adding 'breezy/tests/per_foreign_vcs/test_branch.py' adding 'breezy/tests/per_foreign_vcs/test_repository.py' adding 'breezy/tests/per_interbranch/__init__.py' adding 'breezy/tests/per_interbranch/test_copy_content_into.py' adding 'breezy/tests/per_interbranch/test_fetch.py' adding 'breezy/tests/per_interbranch/test_get.py' adding 'breezy/tests/per_interbranch/test_pull.py' adding 'breezy/tests/per_interbranch/test_push.py' adding 'breezy/tests/per_interrepository/__init__.py' adding 'breezy/tests/per_interrepository/test_fetch.py' adding 'breezy/tests/per_interrepository/test_interrepository.py' adding 'breezy/tests/per_intertree/__init__.py' adding 'breezy/tests/per_intertree/test_compare.py' adding 'breezy/tests/per_intertree/test_file_content_matches.py' adding 'breezy/tests/per_intertree/test_find_path.py' adding 'breezy/tests/per_lock/__init__.py' adding 'breezy/tests/per_lock/test_lock.py' adding 'breezy/tests/per_lock/test_temporary_write_lock.py' adding 'breezy/tests/per_repository/__init__.py' adding 'breezy/tests/per_repository/test_add_fallback_repository.py' adding 'breezy/tests/per_repository/test_break_lock.py' adding 'breezy/tests/per_repository/test_check.py' adding 'breezy/tests/per_repository/test_commit_builder.py' adding 'breezy/tests/per_repository/test_fetch.py' adding 'breezy/tests/per_repository/test_file_graph.py' adding 'breezy/tests/per_repository/test_get_parent_map.py' adding 'breezy/tests/per_repository/test_get_rev_id_for_revno.py' adding 'breezy/tests/per_repository/test_has_revisions.py' adding 'breezy/tests/per_repository/test_has_same_location.py' adding 'breezy/tests/per_repository/test_locking.py' adding 'breezy/tests/per_repository/test_pack.py' adding 'breezy/tests/per_repository/test_reconcile.py' adding 'breezy/tests/per_repository/test_refresh_data.py' adding 'breezy/tests/per_repository/test_repository.py' adding 'breezy/tests/per_repository/test_revision.py' adding 'breezy/tests/per_repository/test_signatures.py' adding 'breezy/tests/per_repository/test_statistics.py' adding 'breezy/tests/per_repository/test_write_group.py' adding 'breezy/tests/per_repository_reference/__init__.py' adding 'breezy/tests/per_repository_reference/test__make_parents_provider.py' adding 'breezy/tests/per_repository_reference/test_add_inventory.py' adding 'breezy/tests/per_repository_reference/test_add_revision.py' adding 'breezy/tests/per_repository_reference/test_add_signature_text.py' adding 'breezy/tests/per_repository_reference/test_all_revision_ids.py' adding 'breezy/tests/per_repository_reference/test_break_lock.py' adding 'breezy/tests/per_repository_reference/test_check.py' adding 'breezy/tests/per_repository_reference/test_commit_with_stacking.py' adding 'breezy/tests/per_repository_reference/test_default_stacking.py' adding 'breezy/tests/per_repository_reference/test_fetch.py' adding 'breezy/tests/per_repository_reference/test_get_record_stream.py' adding 'breezy/tests/per_repository_reference/test_get_rev_id_for_revno.py' adding 'breezy/tests/per_repository_reference/test_graph.py' adding 'breezy/tests/per_repository_reference/test_initialize.py' adding 'breezy/tests/per_repository_reference/test_unlock.py' adding 'breezy/tests/per_tree/__init__.py' adding 'breezy/tests/per_tree/test_annotate_iter.py' adding 'breezy/tests/per_tree/test_archive.py' adding 'breezy/tests/per_tree/test_export.py' adding 'breezy/tests/per_tree/test_get_file_mtime.py' adding 'breezy/tests/per_tree/test_get_file_with_stat.py' adding 'breezy/tests/per_tree/test_get_root_id.py' adding 'breezy/tests/per_tree/test_get_symlink_target.py' adding 'breezy/tests/per_tree/test_ids.py' adding 'breezy/tests/per_tree/test_is_executable.py' adding 'breezy/tests/per_tree/test_iter_search_rules.py' adding 'breezy/tests/per_tree/test_list_files.py' adding 'breezy/tests/per_tree/test_locking.py' adding 'breezy/tests/per_tree/test_path_content_summary.py' adding 'breezy/tests/per_tree/test_revision_tree.py' adding 'breezy/tests/per_tree/test_symlinks.py' adding 'breezy/tests/per_tree/test_test_trees.py' adding 'breezy/tests/per_tree/test_transform.py' adding 'breezy/tests/per_tree/test_tree.py' adding 'breezy/tests/per_tree/test_walkdirs.py' adding 'breezy/tests/per_uifactory/__init__.py' adding 'breezy/tests/per_workingtree/__init__.py' adding 'breezy/tests/per_workingtree/test_add.py' adding 'breezy/tests/per_workingtree/test_add_reference.py' adding 'breezy/tests/per_workingtree/test_annotate_iter.py' adding 'breezy/tests/per_workingtree/test_basis_inventory.py' adding 'breezy/tests/per_workingtree/test_basis_tree.py' adding 'breezy/tests/per_workingtree/test_break_lock.py' adding 'breezy/tests/per_workingtree/test_canonical_path.py' adding 'breezy/tests/per_workingtree/test_changes_from.py' adding 'breezy/tests/per_workingtree/test_check.py' adding 'breezy/tests/per_workingtree/test_check_state.py' adding 'breezy/tests/per_workingtree/test_commit.py' adding 'breezy/tests/per_workingtree/test_content_filters.py' adding 'breezy/tests/per_workingtree/test_eol_conversion.py' adding 'breezy/tests/per_workingtree/test_executable.py' adding 'breezy/tests/per_workingtree/test_flush.py' adding 'breezy/tests/per_workingtree/test_get_file_mtime.py' adding 'breezy/tests/per_workingtree/test_get_parent_ids.py' adding 'breezy/tests/per_workingtree/test_inv.py' adding 'breezy/tests/per_workingtree/test_is_control_filename.py' adding 'breezy/tests/per_workingtree/test_is_ignored.py' adding 'breezy/tests/per_workingtree/test_locking.py' adding 'breezy/tests/per_workingtree/test_merge_from_branch.py' adding 'breezy/tests/per_workingtree/test_mkdir.py' adding 'breezy/tests/per_workingtree/test_move.py' adding 'breezy/tests/per_workingtree/test_nested_specifics.py' adding 'breezy/tests/per_workingtree/test_parents.py' adding 'breezy/tests/per_workingtree/test_paths2ids.py' adding 'breezy/tests/per_workingtree/test_pull.py' adding 'breezy/tests/per_workingtree/test_put_file.py' adding 'breezy/tests/per_workingtree/test_read_working_inventory.py' adding 'breezy/tests/per_workingtree/test_readonly.py' adding 'breezy/tests/per_workingtree/test_remove.py' adding 'breezy/tests/per_workingtree/test_rename_one.py' adding 'breezy/tests/per_workingtree/test_revision_tree.py' adding 'breezy/tests/per_workingtree/test_set_root_id.py' adding 'breezy/tests/per_workingtree/test_shelf_manager.py' adding 'breezy/tests/per_workingtree/test_smart_add.py' adding 'breezy/tests/per_workingtree/test_symlinks.py' adding 'breezy/tests/per_workingtree/test_transform.py' adding 'breezy/tests/per_workingtree/test_uncommit.py' adding 'breezy/tests/per_workingtree/test_unversion.py' adding 'breezy/tests/per_workingtree/test_views.py' adding 'breezy/tests/per_workingtree/test_walkdirs.py' adding 'breezy/tests/per_workingtree/test_workingtree.py' adding 'breezy/tests/ssl_certs/__init__.py' adding 'breezy/tests/ssl_certs/ca.crt' adding 'breezy/tests/ssl_certs/create_ssls.py' adding 'breezy/tests/ssl_certs/server.crt' adding 'breezy/tests/ssl_certs/server_with_pass.key' adding 'breezy/tests/ssl_certs/server_without_pass.key' adding 'breezy/tests/test_patches_data/binary-after-normal.patch' adding 'breezy/tests/test_patches_data/binary.patch' adding 'breezy/tests/test_patches_data/diff' adding 'breezy/tests/test_patches_data/diff-2' adding 'breezy/tests/test_patches_data/diff-3' adding 'breezy/tests/test_patches_data/diff-4' adding 'breezy/tests/test_patches_data/diff-5' adding 'breezy/tests/test_patches_data/diff-6' adding 'breezy/tests/test_patches_data/diff-7' adding 'breezy/tests/test_patches_data/insert_top.patch' adding 'breezy/tests/test_patches_data/mod' adding 'breezy/tests/test_patches_data/mod-2' adding 'breezy/tests/test_patches_data/mod-3' adding 'breezy/tests/test_patches_data/mod-4' adding 'breezy/tests/test_patches_data/mod-5' adding 'breezy/tests/test_patches_data/mod-6' adding 'breezy/tests/test_patches_data/mod-7' adding 'breezy/tests/test_patches_data/orig' adding 'breezy/tests/test_patches_data/orig-2' adding 'breezy/tests/test_patches_data/orig-3' adding 'breezy/tests/test_patches_data/orig-4' adding 'breezy/tests/test_patches_data/orig-5' adding 'breezy/tests/test_patches_data/orig-6' adding 'breezy/tests/test_patches_data/orig-7' adding 'breezy/tests/test_patches_data/patchtext.patch' adding 'breezy/transport/__init__.py' adding 'breezy/transport/brokenrename.py' adding 'breezy/transport/chroot.py' adding 'breezy/transport/decorator.py' adding 'breezy/transport/fakenfs.py' adding 'breezy/transport/fakevfat.py' adding 'breezy/transport/gio_transport.py' adding 'breezy/transport/local.py' adding 'breezy/transport/log.py' adding 'breezy/transport/memory.py' adding 'breezy/transport/nosmart.py' adding 'breezy/transport/pathfilter.py' adding 'breezy/transport/readonly.py' adding 'breezy/transport/remote.py' adding 'breezy/transport/sftp.py' adding 'breezy/transport/ssh.py' adding 'breezy/transport/trace.py' adding 'breezy/transport/unlistable.py' adding 'breezy/transport/http/__init__.py' adding 'breezy/transport/http/ca_bundle.py' adding 'breezy/transport/http/response.py' adding 'breezy/transport/http/urllib.py' adding 'breezy/transport/http/wsgi.py' adding 'breezy/ui/__init__.py' adding 'breezy/ui/text.py' adding 'breezy/util/__init__.py' adding 'breezy/util/simplemapi.py' adding 'breezy/util/tests/__init__.py' adding 'breezy/version_info_formats/__init__.py' adding 'breezy/version_info_formats/format_custom.py' adding 'breezy/version_info_formats/format_python.py' adding 'breezy/version_info_formats/format_rio.py' adding 'breezy/version_info_formats/format_yaml.py' adding 'breezy-3.3.4.data/scripts/brz' adding 'breezy-3.3.4.data/scripts/bzr-receive-pack' adding 'breezy-3.3.4.data/scripts/bzr-upload-pack' adding 'breezy-3.3.4.data/scripts/git-remote-bzr' adding 'breezy-3.3.4.dist-info/COPYING.txt' adding 'breezy-3.3.4.dist-info/METADATA' adding 'breezy-3.3.4.dist-info/WHEEL' adding 'breezy-3.3.4.dist-info/top_level.txt' adding 'breezy-3.3.4.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Successfully built breezy-3.3.4-cp310-cp310-linux_x86_64.whl Finished creating a wheel... Finished executing pypaBuildPhase buildPhase completed in 47 seconds installing Executing pypaInstallPhase Successfully installed breezy-3.3.4-cp310-cp310-linux_x86_64.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4 shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_dirstate_helpers_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_static_tuple_c.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_groupcompress_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_rio_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_rio_rs.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_knit_load_data_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_chk_map_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_btree_serializer_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/bzr/_simple_set_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/_chunks_to_lines_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/_annotator_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/_readdir_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib/python3.10/site-packages/breezy/_known_graph_pyx.cpython-310-x86_64-linux-gnu.so shrinking /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/bin/.brz-wrapped checking for references to /build/ in /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4... patching script interpreter paths in /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4 stripping (with command strip and flags -S -p) in /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/lib /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/bin shrinking RPATHs of ELF executables and libraries in /nix/store/1fqkvvcgvmdww0rd88m1g2f73nbzh76g-python3.10-breezy-3.3.4-dist checking for references to /build/ in /nix/store/1fqkvvcgvmdww0rd88m1g2f73nbzh76g-python3.10-breezy-3.3.4-dist... patching script interpreter paths in /nix/store/1fqkvvcgvmdww0rd88m1g2f73nbzh76g-python3.10-breezy-3.3.4-dist Rewriting #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 to #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12 wrapping `/nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/bin/bzr-receive-pack'... Rewriting #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 to #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12 wrapping `/nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/bin/bzr-upload-pack'... Rewriting #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 to #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12 wrapping `/nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/bin/git-remote-bzr'... Rewriting #! /nix/store/xdqlrixlspkks50m9b0mpvag65m3pf2w-bash-5.2-p15/bin/bash -e to #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12 Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir rewriting symlink /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4/bin/bzr to be relative to /nix/store/d1dk9zsj880400razbrpiljvghwc8974-python3.10-breezy-3.3.4 pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: breezy breezy.bzr.rio building '/nix/store/9y1r4gl4gm9gg95pjq2dggrz307yhda6-nix-prefetch-bzr.drv'... patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building no Makefile or custom buildPhase, doing nothing installing install: creating directory '/nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr' install: creating directory '/nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr/bin' '/nix/store/nmffbbpdfip7pr9800w18m1wrdir70g6-nix-prefetch-bzr' -> '/nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr/bin/nix-prefetch-bzr' post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr checking for references to /build/ in /nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr... patching script interpreter paths in /nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr /nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr/bin/.nix-prefetch-bzr-wrapped: interpreter directive changed from "#! /bin/sh -e" to "/nix/store/xdqlrixlspkks50m9b0mpvag65m3pf2w-bash-5.2-p15/bin/sh -e" stripping (with command strip and flags -S -p) in /nix/store/c049pdlm0dwb0d613wj37sf6nsw5all1-nix-prefetch-bzr/bin building '/nix/store/cncmaasrjpw0v28c6jmvrl7rakzynjlp-nix-prefetch-scripts.drv'... created 10 symlinks in user environment building '/nix/store/32l4axiw5r9wzp65d8jlj0dj5n070hf4-nix-update-source-0.6.3.drv'... Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing setuptools-build-hook Using setuptoolsBuildPhase Using setuptoolsShellHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh unpacking sources unpacking source archive /nix/store/wzn9j3pyfnhzx4fcd3b35gps64gx3b21-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file source/setup.py patching sources updateAutotoolsGnuConfigScriptsPhase configuring no configure script, doing nothing building Executing setuptoolsBuildPhase running bdist_wheel running build running build_py running build_scripts creating build creating build/scripts-3.10 copying and adjusting bin/nix-update-source -> build/scripts-3.10 changing mode of build/scripts-3.10/nix-update-source from 644 to 755 /nix/store/4d9fqsbh5gb8fqhwcqd9cjkd9icrzqds-python3.10-setuptools-68.0.0/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-x86_64/wheel running install running install_lib warning: install_lib: 'build/lib' does not exist -- no Python modules to install running install_egg_info running egg_info creating nix_update_source.egg-info writing nix_update_source.egg-info/PKG-INFO writing dependency_links to nix_update_source.egg-info/dependency_links.txt writing top-level names to nix_update_source.egg-info/top_level.txt writing manifest file 'nix_update_source.egg-info/SOURCES.txt' reading manifest file 'nix_update_source.egg-info/SOURCES.txt' adding license file 'LICENCE' writing manifest file 'nix_update_source.egg-info/SOURCES.txt' Copying nix_update_source.egg-info to build/bdist.linux-x86_64/wheel/nix_update_source-0.6.3-py3.10.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/nix_update_source-0.6.3.data creating build/bdist.linux-x86_64/wheel/nix_update_source-0.6.3.data/scripts copying build/scripts-3.10/nix-update-source -> build/bdist.linux-x86_64/wheel/nix_update_source-0.6.3.data/scripts changing mode of build/bdist.linux-x86_64/wheel/nix_update_source-0.6.3.data/scripts/nix-update-source to 755 creating build/bdist.linux-x86_64/wheel/nix_update_source-0.6.3.dist-info/WHEEL creating 'dist/nix_update_source-0.6.3-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'nix_update_source-0.6.3.data/scripts/nix-update-source' adding 'nix_update_source-0.6.3.dist-info/LICENCE' adding 'nix_update_source-0.6.3.dist-info/METADATA' adding 'nix_update_source-0.6.3.dist-info/WHEEL' adding 'nix_update_source-0.6.3.dist-info/top_level.txt' adding 'nix_update_source-0.6.3.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Finished executing setuptoolsBuildPhase installing Executing pypaInstallPhase Successfully installed nix_update_source-0.6.3-py3-none-any.whl Finished executing pypaInstallPhase pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase post-installation fixup shrinking RPATHs of ELF executables and libraries in /nix/store/2f0c1ml6gvh9v51ddbpvdp3phq2cx8gl-nix-update-source-0.6.3 checking for references to /build/ in /nix/store/2f0c1ml6gvh9v51ddbpvdp3phq2cx8gl-nix-update-source-0.6.3... patching script interpreter paths in /nix/store/2f0c1ml6gvh9v51ddbpvdp3phq2cx8gl-nix-update-source-0.6.3 stripping (with command strip and flags -S -p) in /nix/store/2f0c1ml6gvh9v51ddbpvdp3phq2cx8gl-nix-update-source-0.6.3/lib /nix/store/2f0c1ml6gvh9v51ddbpvdp3phq2cx8gl-nix-update-source-0.6.3/bin shrinking RPATHs of ELF executables and libraries in /nix/store/7b9a97jh49i5a594facdq5ygqhfmj50q-nix-update-source-0.6.3-dist checking for references to /build/ in /nix/store/7b9a97jh49i5a594facdq5ygqhfmj50q-nix-update-source-0.6.3-dist... patching script interpreter paths in /nix/store/7b9a97jh49i5a594facdq5ygqhfmj50q-nix-update-source-0.6.3-dist Rewriting #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12/bin/python3.10 to #!/nix/store/pzf6dnxg8gf04xazzjdwarm7s03cbrgz-python3-3.10.12 wrapping `/nix/store/2f0c1ml6gvh9v51ddbpvdp3phq2cx8gl-nix-update-source-0.6.3/bin/nix-update-source'... Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir pythonCatchConflictsPhase /nix/store/q2zpnf017gccs9w9mb0ikdqhkf0k5v82-catch_conflicts.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html import pkg_resources pythonRemoveBinBytecodePhase pythonImportsCheckPhase Executing pythonImportsCheckPhase building '/nix/store/g3b55d2lq74xf112a0p15aki99qclsb6-packages.json.drv'... Going to be running update for following packages: - nix-update-source-0.6.3 Press Enter key to continue... Running update for: - nix-update-source-0.6.3: UPDATING ... - nix-update-source-0.6.3: ERROR --- SHOWING ERROR LOG FOR nix-update-source-0.6.3 ---------------------- env: ‘#!/nix/store/xdqlrixlspkks50m9b0mpvag65m3pf2w-bash-5.2-p15/bin/bash\nset -e\necho\ncd /var/cache/nixpkgs-update/worker/worktree/nix-update-source/pkgs/tools/package-management/nix-update-source\n/nix/store/2f0c1ml6gvh9v51ddbpvdp3phq2cx8gl-nix-update-source-0.6.3/bin/nix-update-source \\\n --prompt version \\\n --replace-attr version \\\n --set owner timbertson \\\n --set repo nix-update-source \\\n --set type fetchFromGitHub \\\n --set rev 'version-{version}' \\\n --modify-nix default.nix\n’: No such file or directory env: use -[v]S to pass options in shebang lines --- SHOWING ERROR LOG FOR nix-update-source-0.6.3 ---------------------- The update script for nix-update-source-0.6.3 failed with exit code 127