=>> Building www/py-django-contrib-comments build started at Tue Jun 2 05:48:08 JST 2026 port directory: /usr/ports/www/py-django-contrib-comments package name: py311-django-contrib-comments-2.2.0_3 building for: FreeBSD curamd64-setuptools-job-02 16.0-CURRENT FreeBSD 16.0-CURRENT 1600018 amd64 maintained by: bofh@FreeBSD.org Makefile datestamp: -rw-r--r-- 1 root wheel 666 May 2 10:26 /usr/ports/www/py-django-contrib-comments/Makefile Ports top last git commit: a8b187544 Ports top unclean checkout: yes Port dir last git commit: a8b187544 Port dir unclean checkout: no Poudriere version: poudriere-git-3.4.4 Host OSVERSION: 1600018 Jail OSVERSION: 1600018 Job Id: 02 ---Begin Environment--- SHELL=/bin/sh OSVERSION=1600018 UNAME_v=FreeBSD 16.0-CURRENT 1600018 UNAME_r=16.0-CURRENT BLOCKSIZE=K MAIL=/var/mail/root MM_CHARSET=UTF-8 LANG=C.UTF-8 STATUS=1 HOME=/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin MAKE_OBJDIR_CHECK_WRITABLE=0 LOCALBASE=/usr/local USER=root POUDRIERE_NAME=poudriere-git LIBEXECPREFIX=/usr/local/libexec/poudriere POUDRIERE_VERSION=3.4.4 MASTERMNT=/usr/local/poudriere/data/.m/curamd64-setuptools/ref LC_COLLATE=C POUDRIERE_BUILD_TYPE=bulk PACKAGE_BUILDING=yes SAVED_TERM=tmux-256color GID=0 OUTPUT_REDIRECTED_STDERR=4 OUTPUT_REDIRECTED=1 UID=0 PWD=/usr/local/poudriere/data/.m/curamd64-setuptools/02/.p OUTPUT_REDIRECTED_STDOUT=3 P_PORTS_FEATURES=FLAVORS SUBPACKAGES SELECTED_OPTIONS MASTERNAME=curamd64-setuptools SCRIPTPREFIX=/usr/local/share/poudriere SCRIPTNAME=bulk.sh OLDPWD=/usr/local/poudriere/data/.m/curamd64-setuptools/ref/.p/pool POUDRIERE_PKGNAME=poudriere-git-3.4.4 SCRIPTPATH=/usr/local/share/poudriere/bulk.sh POUDRIEREPATH=/usr/local/bin/poudriere ---End Environment--- ---Begin Poudriere Port Flags/Env--- PORT_FLAGS= PKGENV= FLAVOR=py311 MAKE_ARGS= FLAVOR=py311 ---End Poudriere Port Flags/Env--- ---Begin OPTIONS List--- ---End OPTIONS List--- --MAINTAINER-- bofh@FreeBSD.org --End MAINTAINER-- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- PYTHON="/usr/local/bin/python3.11" XDG_DATA_HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311 XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311 XDG_CACHE_HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/.cache HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311 TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV-- --MAKE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311 XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311 XDG_CACHE_HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/.cache HOME=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311 TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES LDSHARED="cc -shared" PYTHONDONTWRITEBYTECODE= PYTHONOPTIMIZE= PREFIX=/usr/local LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing " CPP="cpp" CPPFLAGS="" LDFLAGS=" " LIBS="" CXX="c++" CXXFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing " BSD_INSTALL_PROGRAM="install -s -m 555" BSD_INSTALL_LIB="install -s -m 0644" BSD_INSTALL_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" --End MAKE_ENV-- --PLIST_SUB-- PYTHON_INCLUDEDIR=include/python3.11 PYTHON_LIBDIR=lib/python3.11 PYTHON_PLATFORM=freebsd16 PYTHON_SITELIBDIR=lib/python3.11/site-packages PYTHON_SUFFIX=311 PYTHON_BASESUFFIX=311 PYTHON_TAG=.cpython-311 PYTHON_SOABI=.cpython-311 PYTHON_VER=3.11 PYTHON_BASEVER=3.11 PYTHON_VERSION=python3.11 PYTHON2="@comment " PYTHON3="" OSREL=16.0 PREFIX=%D LOCALBASE=/usr/local RESETPREFIX=/usr/local LIB32DIR=lib DOCSDIR="share/doc/django-contrib-comments" EXAMPLESDIR="share/examples/django-contrib-comments" DATADIR="share/django-contrib-comments" WWWDIR="www/django-contrib-comments" ETCDIR="etc/django-contrib-comments" --End PLIST_SUB-- --SUB_LIST-- PYTHON_INCLUDEDIR=/usr/local/include/python3.11 PYTHON_LIBDIR=/usr/local/lib/python3.11 PYTHON_PLATFORM=freebsd16 PYTHON_SITELIBDIR=/usr/local/lib/python3.11/site-packages PYTHON_SUFFIX=311 PYTHON_BASESUFFIX=311 PYTHON_TAG=.cpython-311 PYTHON_SOABI=.cpython-311 PYTHON_VER=3.11 PYTHON_BASEVER=3.11 PYTHON_VERSION=python3.11 PYTHON2="@comment " PYTHON3="" PREFIX=/usr/local LOCALBASE=/usr/local DATADIR=/usr/local/share/django-contrib-comments DOCSDIR=/usr/local/share/doc/django-contrib-comments EXAMPLESDIR=/usr/local/share/examples/django-contrib-comments WWWDIR=/usr/local/www/django-contrib-comments ETCDIR=/usr/local/etc/django-contrib-comments --End SUB_LIST-- ---Begin make.conf--- DEFAULT_VERSIONS+= magick=7-x11 DEFAULT_VERSIONS+= pgsql=18 DEFAULT_VERSIONS+= ssl=openssl japanese_fcitx5_mozc_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_UNSET= JAWIKI x11_wm_hikari_SET= GAMMA INPUTMETHOD LAYERSHELL SCREENCOPY VIRTUALINPUT X11 .if $(.CURDIR:M*/x11-wm/hikari) WITH_DEBUG= YES .endif USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs PORTSDIR=/usr/ports PACKAGES=/packages DISTDIR=/distfiles FORCE_PACKAGE=yes PACKAGE_BUILDING=yes PACKAGE_BUILDING_FLAVORS=yes #### #### DEFAULT_VERSIONS+= magick=7-x11 DEFAULT_VERSIONS+= pgsql=18 DEFAULT_VERSIONS+= ssl=openssl japanese_fcitx5_mozc_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_UNSET= JAWIKI x11_wm_hikari_SET= GAMMA INPUTMETHOD LAYERSHELL SCREENCOPY VIRTUALINPUT X11 .if $(.CURDIR:M*/x11-wm/hikari) WITH_DEBUG= YES .endif #### Misc Poudriere #### .include "/etc/make.conf.ports_env" DISABLE_MAKE_JOBS=poudriere ---End make.conf--- --Resource limits-- cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 33554432 stack size (kbytes, -s) 524288 core file size (512-blocks, -c) unlimited max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) unlimited max user processes (-u) 12099 open files (-n) 8192 virtual mem size (kbytes, -v) unlimited swap limit (kbytes, -w) unlimited socket buffer size (bytes, -b) unlimited pseudo-terminals (-p) unlimited kqueues (-k) unlimited umtx shared locks (-o) unlimited pipebuf (-y) unlimited --End resource limits-- =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> License BSD3CLAUSE accepted by the user =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py311-django-contrib-comments-2.2.0_3 depends on file: /usr/local/sbin/pkg - not found ===> Installing existing package /packages/All/pkg-2.7.5.pkg [curamd64-setuptools-job-02] Installing pkg-2.7.5... [curamd64-setuptools-job-02] Extracting pkg-2.7.5: .......... done ===> py311-django-contrib-comments-2.2.0_3 depends on file: /usr/local/sbin/pkg - found ===> Returning to build of py311-django-contrib-comments-2.2.0_3 =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0 ===> License BSD3CLAUSE accepted by the user => django-contrib-comments-2.2.0.tar.gz doesn't seem to exist in /portdistfiles. => Attempting to fetch https://files.pythonhosted.org/packages/source/d/django-contrib-comments/django-contrib-comments-2.2.0.tar.gz django-contrib-comments-2.2.0.tar.gz 849 kB 16 MBps 00s ===> Fetching all distfiles required by py311-django-contrib-comments-2.2.0_3 for building =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0 ===> License BSD3CLAUSE accepted by the user ===> Fetching all distfiles required by py311-django-contrib-comments-2.2.0_3 for building => SHA256 Checksum OK for django-contrib-comments-2.2.0.tar.gz. =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> License BSD3CLAUSE accepted by the user ===> Fetching all distfiles required by py311-django-contrib-comments-2.2.0_3 for building ===> Extracting for py311-django-contrib-comments-2.2.0_3 => SHA256 Checksum OK for django-contrib-comments-2.2.0.tar.gz. =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Patching for py311-django-contrib-comments-2.2.0_3 =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py311-django-contrib-comments-2.2.0_3 depends on package: py311-setuptools>=63.1.0 - not found ===> Installing existing package /packages/All/py311-setuptools-81.0.0.pkg [curamd64-setuptools-job-02] Installing py311-setuptools-81.0.0... [curamd64-setuptools-job-02] `-- Installing py311-more-itertools-10.6.0... [curamd64-setuptools-job-02] | `-- Installing python311-3.11.15_2... [curamd64-setuptools-job-02] | | `-- Installing gettext-runtime-1.0... [curamd64-setuptools-job-02] | | `-- Installing indexinfo-0.3.1_1... [curamd64-setuptools-job-02] | | `-- Extracting indexinfo-0.3.1_1: .... done [curamd64-setuptools-job-02] | | `-- Extracting gettext-runtime-1.0: .......... done [curamd64-setuptools-job-02] | | `-- Installing libffi-3.5.1... [curamd64-setuptools-job-02] | | `-- Extracting libffi-3.5.1: .......... done [curamd64-setuptools-job-02] | | `-- Installing mpdecimal-4.0.1... [curamd64-setuptools-job-02] | | `-- Extracting mpdecimal-4.0.1: .......... done [curamd64-setuptools-job-02] | | `-- Installing openssl-3.0.20,1... [curamd64-setuptools-job-02] | | `-- Extracting openssl-3.0.20,1: .......... done [curamd64-setuptools-job-02] | | `-- Installing readline-8.3.3... [curamd64-setuptools-job-02] | | `-- Extracting readline-8.3.3: .......... done [curamd64-setuptools-job-02] | `-- Extracting python311-3.11.15_2: .......... done [curamd64-setuptools-job-02] `-- Extracting py311-more-itertools-10.6.0: .......... done [curamd64-setuptools-job-02] `-- Installing py311-packaging-26.2... [curamd64-setuptools-job-02] `-- Extracting py311-packaging-26.2: .......... done [curamd64-setuptools-job-02] `-- Installing py311-wheel-0.47.0... [curamd64-setuptools-job-02] `-- Extracting py311-wheel-0.47.0: .......... done [curamd64-setuptools-job-02] Extracting py311-setuptools-81.0.0: .......... done ===== Message from python311-3.11.15_2: -- Note that some standard Python modules are provided as separate ports as they require additional dependencies. They are available as: py311-gdbm databases/py-gdbm@py311 py311-sqlite3 databases/py-sqlite3@py311 py311-tkinter x11-toolkits/py-tkinter@py311 ===> py311-django-contrib-comments-2.2.0_3 depends on package: py311-setuptools>=63.1.0 - found ===> Returning to build of py311-django-contrib-comments-2.2.0_3 ===> py311-django-contrib-comments-2.2.0_3 depends on file: /usr/local/bin/python3.11 - found =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Configuring for py311-django-contrib-comments-2.2.0_3 /usr/local/lib/python3.11/site-packages/setuptools/_distutils/dist.py:287: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/local/lib/python3.11/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running config =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Building for py311-django-contrib-comments-2.2.0_3 /usr/local/lib/python3.11/site-packages/setuptools/_distutils/dist.py:287: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/local/lib/python3.11/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running build running build_py creating build/lib/django_comments copying django_comments/__init__.py -> build/lib/django_comments copying django_comments/abstracts.py -> build/lib/django_comments copying django_comments/admin.py -> build/lib/django_comments copying django_comments/apps.py -> build/lib/django_comments copying django_comments/compat.py -> build/lib/django_comments copying django_comments/feeds.py -> build/lib/django_comments copying django_comments/forms.py -> build/lib/django_comments copying django_comments/managers.py -> build/lib/django_comments copying django_comments/models.py -> build/lib/django_comments copying django_comments/moderation.py -> build/lib/django_comments copying django_comments/signals.py -> build/lib/django_comments copying django_comments/urls.py -> build/lib/django_comments creating build/lib/django_comments/management copying django_comments/management/__init__.py -> build/lib/django_comments/management creating build/lib/django_comments/migrations copying django_comments/migrations/0001_initial.py -> build/lib/django_comments/migrations copying django_comments/migrations/0002_update_user_email_field_length.py -> build/lib/django_comments/migrations copying django_comments/migrations/0003_add_submit_date_index.py -> build/lib/django_comments/migrations copying django_comments/migrations/0004_add_object_pk_is_removed_index.py -> build/lib/django_comments/migrations copying django_comments/migrations/__init__.py -> build/lib/django_comments/migrations creating build/lib/django_comments/templatetags copying django_comments/templatetags/__init__.py -> build/lib/django_comments/templatetags copying django_comments/templatetags/comments.py -> build/lib/django_comments/templatetags creating build/lib/django_comments/views copying django_comments/views/__init__.py -> build/lib/django_comments/views copying django_comments/views/comments.py -> build/lib/django_comments/views copying django_comments/views/moderation.py -> build/lib/django_comments/views copying django_comments/views/utils.py -> build/lib/django_comments/views creating build/lib/django_comments/management/commands copying django_comments/management/commands/__init__.py -> build/lib/django_comments/management/commands copying django_comments/management/commands/delete_stale_comments.py -> build/lib/django_comments/management/commands running egg_info writing django_contrib_comments.egg-info/PKG-INFO writing dependency_links to django_contrib_comments.egg-info/dependency_links.txt writing requirements to django_contrib_comments.egg-info/requires.txt writing top-level names to django_contrib_comments.egg-info/top_level.txt reading manifest file 'django_contrib_comments.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE.txt' writing manifest file 'django_contrib_comments.egg-info/SOURCES.txt' /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fy_NL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.fy_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_comments.locale.fy_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_comments.locale.fy_NL.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.fy_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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.templates.comments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.templates.comments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.templates.comments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.templates.comments' to be distributed and are already explicitly excluding 'django_comments.templates.comments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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_comments/locale/af/LC_MESSAGES copying django_comments/locale/af/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/af/LC_MESSAGES copying django_comments/locale/af/LC_MESSAGES/django.po -> build/lib/django_comments/locale/af/LC_MESSAGES creating build/lib/django_comments/locale/ar/LC_MESSAGES copying django_comments/locale/ar/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ar/LC_MESSAGES copying django_comments/locale/ar/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ar/LC_MESSAGES creating build/lib/django_comments/locale/az/LC_MESSAGES copying django_comments/locale/az/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/az/LC_MESSAGES copying django_comments/locale/az/LC_MESSAGES/django.po -> build/lib/django_comments/locale/az/LC_MESSAGES creating build/lib/django_comments/locale/be/LC_MESSAGES copying django_comments/locale/be/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/be/LC_MESSAGES copying django_comments/locale/be/LC_MESSAGES/django.po -> build/lib/django_comments/locale/be/LC_MESSAGES creating build/lib/django_comments/locale/bg/LC_MESSAGES copying django_comments/locale/bg/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/bg/LC_MESSAGES copying django_comments/locale/bg/LC_MESSAGES/django.po -> build/lib/django_comments/locale/bg/LC_MESSAGES creating build/lib/django_comments/locale/bn/LC_MESSAGES copying django_comments/locale/bn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/bn/LC_MESSAGES copying django_comments/locale/bn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/bn/LC_MESSAGES creating build/lib/django_comments/locale/br/LC_MESSAGES copying django_comments/locale/br/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/br/LC_MESSAGES copying django_comments/locale/br/LC_MESSAGES/django.po -> build/lib/django_comments/locale/br/LC_MESSAGES creating build/lib/django_comments/locale/bs/LC_MESSAGES copying django_comments/locale/bs/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/bs/LC_MESSAGES copying django_comments/locale/bs/LC_MESSAGES/django.po -> build/lib/django_comments/locale/bs/LC_MESSAGES creating build/lib/django_comments/locale/ca/LC_MESSAGES copying django_comments/locale/ca/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ca/LC_MESSAGES copying django_comments/locale/ca/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ca/LC_MESSAGES creating build/lib/django_comments/locale/cs/LC_MESSAGES copying django_comments/locale/cs/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/cs/LC_MESSAGES copying django_comments/locale/cs/LC_MESSAGES/django.po -> build/lib/django_comments/locale/cs/LC_MESSAGES creating build/lib/django_comments/locale/cy/LC_MESSAGES copying django_comments/locale/cy/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/cy/LC_MESSAGES copying django_comments/locale/cy/LC_MESSAGES/django.po -> build/lib/django_comments/locale/cy/LC_MESSAGES creating build/lib/django_comments/locale/da/LC_MESSAGES copying django_comments/locale/da/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/da/LC_MESSAGES copying django_comments/locale/da/LC_MESSAGES/django.po -> build/lib/django_comments/locale/da/LC_MESSAGES creating build/lib/django_comments/locale/de/LC_MESSAGES copying django_comments/locale/de/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/de/LC_MESSAGES copying django_comments/locale/de/LC_MESSAGES/django.po -> build/lib/django_comments/locale/de/LC_MESSAGES creating build/lib/django_comments/locale/el/LC_MESSAGES copying django_comments/locale/el/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/el/LC_MESSAGES copying django_comments/locale/el/LC_MESSAGES/django.po -> build/lib/django_comments/locale/el/LC_MESSAGES creating build/lib/django_comments/locale/en/LC_MESSAGES copying django_comments/locale/en/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/en/LC_MESSAGES copying django_comments/locale/en/LC_MESSAGES/django.po -> build/lib/django_comments/locale/en/LC_MESSAGES creating build/lib/django_comments/locale/en_GB/LC_MESSAGES copying django_comments/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/en_GB/LC_MESSAGES copying django_comments/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django_comments/locale/en_GB/LC_MESSAGES creating build/lib/django_comments/locale/eo/LC_MESSAGES copying django_comments/locale/eo/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/eo/LC_MESSAGES copying django_comments/locale/eo/LC_MESSAGES/django.po -> build/lib/django_comments/locale/eo/LC_MESSAGES creating build/lib/django_comments/locale/es/LC_MESSAGES copying django_comments/locale/es/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/es/LC_MESSAGES copying django_comments/locale/es/LC_MESSAGES/django.po -> build/lib/django_comments/locale/es/LC_MESSAGES creating build/lib/django_comments/locale/es_AR/LC_MESSAGES copying django_comments/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/es_AR/LC_MESSAGES copying django_comments/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django_comments/locale/es_AR/LC_MESSAGES creating build/lib/django_comments/locale/es_MX/LC_MESSAGES copying django_comments/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/es_MX/LC_MESSAGES copying django_comments/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django_comments/locale/es_MX/LC_MESSAGES creating build/lib/django_comments/locale/et/LC_MESSAGES copying django_comments/locale/et/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/et/LC_MESSAGES copying django_comments/locale/et/LC_MESSAGES/django.po -> build/lib/django_comments/locale/et/LC_MESSAGES creating build/lib/django_comments/locale/eu/LC_MESSAGES copying django_comments/locale/eu/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/eu/LC_MESSAGES copying django_comments/locale/eu/LC_MESSAGES/django.po -> build/lib/django_comments/locale/eu/LC_MESSAGES creating build/lib/django_comments/locale/fa/LC_MESSAGES copying django_comments/locale/fa/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fa/LC_MESSAGES copying django_comments/locale/fa/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fa/LC_MESSAGES creating build/lib/django_comments/locale/fi/LC_MESSAGES copying django_comments/locale/fi/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fi/LC_MESSAGES copying django_comments/locale/fi/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fi/LC_MESSAGES creating build/lib/django_comments/locale/fr/LC_MESSAGES copying django_comments/locale/fr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fr/LC_MESSAGES copying django_comments/locale/fr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fr/LC_MESSAGES creating build/lib/django_comments/locale/fy_NL/LC_MESSAGES copying django_comments/locale/fy_NL/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fy_NL/LC_MESSAGES copying django_comments/locale/fy_NL/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fy_NL/LC_MESSAGES creating build/lib/django_comments/locale/ga/LC_MESSAGES copying django_comments/locale/ga/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ga/LC_MESSAGES copying django_comments/locale/ga/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ga/LC_MESSAGES creating build/lib/django_comments/locale/gd/LC_MESSAGES copying django_comments/locale/gd/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/gd/LC_MESSAGES copying django_comments/locale/gd/LC_MESSAGES/django.po -> build/lib/django_comments/locale/gd/LC_MESSAGES creating build/lib/django_comments/locale/gl/LC_MESSAGES copying django_comments/locale/gl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/gl/LC_MESSAGES copying django_comments/locale/gl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/gl/LC_MESSAGES creating build/lib/django_comments/locale/he/LC_MESSAGES copying django_comments/locale/he/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/he/LC_MESSAGES copying django_comments/locale/he/LC_MESSAGES/django.po -> build/lib/django_comments/locale/he/LC_MESSAGES creating build/lib/django_comments/locale/hi/LC_MESSAGES copying django_comments/locale/hi/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/hi/LC_MESSAGES copying django_comments/locale/hi/LC_MESSAGES/django.po -> build/lib/django_comments/locale/hi/LC_MESSAGES creating build/lib/django_comments/locale/hr/LC_MESSAGES copying django_comments/locale/hr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/hr/LC_MESSAGES copying django_comments/locale/hr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/hr/LC_MESSAGES creating build/lib/django_comments/locale/hu/LC_MESSAGES copying django_comments/locale/hu/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/hu/LC_MESSAGES copying django_comments/locale/hu/LC_MESSAGES/django.po -> build/lib/django_comments/locale/hu/LC_MESSAGES creating build/lib/django_comments/locale/ia/LC_MESSAGES copying django_comments/locale/ia/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ia/LC_MESSAGES copying django_comments/locale/ia/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ia/LC_MESSAGES creating build/lib/django_comments/locale/id/LC_MESSAGES copying django_comments/locale/id/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/id/LC_MESSAGES copying django_comments/locale/id/LC_MESSAGES/django.po -> build/lib/django_comments/locale/id/LC_MESSAGES creating build/lib/django_comments/locale/is/LC_MESSAGES copying django_comments/locale/is/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/is/LC_MESSAGES copying django_comments/locale/is/LC_MESSAGES/django.po -> build/lib/django_comments/locale/is/LC_MESSAGES creating build/lib/django_comments/locale/it/LC_MESSAGES copying django_comments/locale/it/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/it/LC_MESSAGES copying django_comments/locale/it/LC_MESSAGES/django.po -> build/lib/django_comments/locale/it/LC_MESSAGES creating build/lib/django_comments/locale/ja/LC_MESSAGES copying django_comments/locale/ja/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ja/LC_MESSAGES copying django_comments/locale/ja/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ja/LC_MESSAGES creating build/lib/django_comments/locale/ka/LC_MESSAGES copying django_comments/locale/ka/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ka/LC_MESSAGES copying django_comments/locale/ka/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ka/LC_MESSAGES creating build/lib/django_comments/locale/kk/LC_MESSAGES copying django_comments/locale/kk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/kk/LC_MESSAGES copying django_comments/locale/kk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/kk/LC_MESSAGES creating build/lib/django_comments/locale/km/LC_MESSAGES copying django_comments/locale/km/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/km/LC_MESSAGES copying django_comments/locale/km/LC_MESSAGES/django.po -> build/lib/django_comments/locale/km/LC_MESSAGES creating build/lib/django_comments/locale/kn/LC_MESSAGES copying django_comments/locale/kn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/kn/LC_MESSAGES copying django_comments/locale/kn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/kn/LC_MESSAGES creating build/lib/django_comments/locale/ko/LC_MESSAGES copying django_comments/locale/ko/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ko/LC_MESSAGES copying django_comments/locale/ko/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ko/LC_MESSAGES creating build/lib/django_comments/locale/lt/LC_MESSAGES copying django_comments/locale/lt/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/lt/LC_MESSAGES copying django_comments/locale/lt/LC_MESSAGES/django.po -> build/lib/django_comments/locale/lt/LC_MESSAGES creating build/lib/django_comments/locale/lv/LC_MESSAGES copying django_comments/locale/lv/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/lv/LC_MESSAGES copying django_comments/locale/lv/LC_MESSAGES/django.po -> build/lib/django_comments/locale/lv/LC_MESSAGES creating build/lib/django_comments/locale/mk/LC_MESSAGES copying django_comments/locale/mk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/mk/LC_MESSAGES copying django_comments/locale/mk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/mk/LC_MESSAGES creating build/lib/django_comments/locale/ml/LC_MESSAGES copying django_comments/locale/ml/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ml/LC_MESSAGES copying django_comments/locale/ml/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ml/LC_MESSAGES creating build/lib/django_comments/locale/mn/LC_MESSAGES copying django_comments/locale/mn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/mn/LC_MESSAGES copying django_comments/locale/mn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/mn/LC_MESSAGES creating build/lib/django_comments/locale/nb/LC_MESSAGES copying django_comments/locale/nb/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/nb/LC_MESSAGES copying django_comments/locale/nb/LC_MESSAGES/django.po -> build/lib/django_comments/locale/nb/LC_MESSAGES creating build/lib/django_comments/locale/ne/LC_MESSAGES copying django_comments/locale/ne/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ne/LC_MESSAGES copying django_comments/locale/ne/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ne/LC_MESSAGES creating build/lib/django_comments/locale/nl/LC_MESSAGES copying django_comments/locale/nl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/nl/LC_MESSAGES copying django_comments/locale/nl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/nl/LC_MESSAGES creating build/lib/django_comments/locale/nn/LC_MESSAGES copying django_comments/locale/nn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/nn/LC_MESSAGES copying django_comments/locale/nn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/nn/LC_MESSAGES creating build/lib/django_comments/locale/pa/LC_MESSAGES copying django_comments/locale/pa/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pa/LC_MESSAGES copying django_comments/locale/pa/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pa/LC_MESSAGES creating build/lib/django_comments/locale/pl/LC_MESSAGES copying django_comments/locale/pl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pl/LC_MESSAGES copying django_comments/locale/pl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pl/LC_MESSAGES creating build/lib/django_comments/locale/pt/LC_MESSAGES copying django_comments/locale/pt/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pt/LC_MESSAGES copying django_comments/locale/pt/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pt/LC_MESSAGES creating build/lib/django_comments/locale/pt_BR/LC_MESSAGES copying django_comments/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pt_BR/LC_MESSAGES copying django_comments/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pt_BR/LC_MESSAGES creating build/lib/django_comments/locale/ro/LC_MESSAGES copying django_comments/locale/ro/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ro/LC_MESSAGES copying django_comments/locale/ro/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ro/LC_MESSAGES creating build/lib/django_comments/locale/ru/LC_MESSAGES copying django_comments/locale/ru/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ru/LC_MESSAGES copying django_comments/locale/ru/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ru/LC_MESSAGES creating build/lib/django_comments/locale/sk/LC_MESSAGES copying django_comments/locale/sk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sk/LC_MESSAGES copying django_comments/locale/sk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sk/LC_MESSAGES creating build/lib/django_comments/locale/sl/LC_MESSAGES copying django_comments/locale/sl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sl/LC_MESSAGES copying django_comments/locale/sl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sl/LC_MESSAGES creating build/lib/django_comments/locale/sq/LC_MESSAGES copying django_comments/locale/sq/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sq/LC_MESSAGES copying django_comments/locale/sq/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sq/LC_MESSAGES creating build/lib/django_comments/locale/sr/LC_MESSAGES copying django_comments/locale/sr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sr/LC_MESSAGES copying django_comments/locale/sr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sr/LC_MESSAGES creating build/lib/django_comments/locale/sr_Latn/LC_MESSAGES copying django_comments/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sr_Latn/LC_MESSAGES copying django_comments/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sr_Latn/LC_MESSAGES creating build/lib/django_comments/locale/sv/LC_MESSAGES copying django_comments/locale/sv/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sv/LC_MESSAGES copying django_comments/locale/sv/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sv/LC_MESSAGES creating build/lib/django_comments/locale/sw/LC_MESSAGES copying django_comments/locale/sw/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sw/LC_MESSAGES copying django_comments/locale/sw/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sw/LC_MESSAGES creating build/lib/django_comments/locale/ta/LC_MESSAGES copying django_comments/locale/ta/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ta/LC_MESSAGES copying django_comments/locale/ta/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ta/LC_MESSAGES creating build/lib/django_comments/locale/te/LC_MESSAGES copying django_comments/locale/te/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/te/LC_MESSAGES copying django_comments/locale/te/LC_MESSAGES/django.po -> build/lib/django_comments/locale/te/LC_MESSAGES creating build/lib/django_comments/locale/th/LC_MESSAGES copying django_comments/locale/th/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/th/LC_MESSAGES copying django_comments/locale/th/LC_MESSAGES/django.po -> build/lib/django_comments/locale/th/LC_MESSAGES creating build/lib/django_comments/locale/tr/LC_MESSAGES copying django_comments/locale/tr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/tr/LC_MESSAGES copying django_comments/locale/tr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/tr/LC_MESSAGES creating build/lib/django_comments/locale/tt/LC_MESSAGES copying django_comments/locale/tt/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/tt/LC_MESSAGES copying django_comments/locale/tt/LC_MESSAGES/django.po -> build/lib/django_comments/locale/tt/LC_MESSAGES creating build/lib/django_comments/locale/uk/LC_MESSAGES copying django_comments/locale/uk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/uk/LC_MESSAGES copying django_comments/locale/uk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/uk/LC_MESSAGES creating build/lib/django_comments/locale/ur/LC_MESSAGES copying django_comments/locale/ur/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ur/LC_MESSAGES copying django_comments/locale/ur/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ur/LC_MESSAGES creating build/lib/django_comments/locale/vi/LC_MESSAGES copying django_comments/locale/vi/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/vi/LC_MESSAGES copying django_comments/locale/vi/LC_MESSAGES/django.po -> build/lib/django_comments/locale/vi/LC_MESSAGES creating build/lib/django_comments/locale/zh_Hans/LC_MESSAGES copying django_comments/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/zh_Hans/LC_MESSAGES copying django_comments/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django_comments/locale/zh_Hans/LC_MESSAGES creating build/lib/django_comments/locale/zh_Hant/LC_MESSAGES copying django_comments/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/zh_Hant/LC_MESSAGES copying django_comments/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django_comments/locale/zh_Hant/LC_MESSAGES creating build/lib/django_comments/templates/comments copying django_comments/templates/comments/400-debug.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/approve.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/approved.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/base.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/delete.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/deleted.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/flag.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/flagged.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/form.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/list.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/posted.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/preview.html -> build/lib/django_comments/templates/comments =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py311-django-contrib-comments-2.2.0_3 depends on package: py311-django42>=2.2 - not found ===> Installing existing package /packages/All/py311-django42-4.2.30.pkg [curamd64-setuptools-job-02] Installing py311-django42-4.2.30... [curamd64-setuptools-job-02] `-- Installing py311-asgiref-3.11.1... [curamd64-setuptools-job-02] `-- Extracting py311-asgiref-3.11.1: .......... done [curamd64-setuptools-job-02] `-- Installing py311-sqlite3-3.11.15_10... [curamd64-setuptools-job-02] | `-- Installing sqlite3-3.50.4_2,1... [curamd64-setuptools-job-02] | | `-- Installing libedit-3.1.20251016_1,1... [curamd64-setuptools-job-02] | | `-- Extracting libedit-3.1.20251016_1,1: .......... done [curamd64-setuptools-job-02] | `-- Extracting sqlite3-3.50.4_2,1: .......... done [curamd64-setuptools-job-02] `-- Extracting py311-sqlite3-3.11.15_10: ......... done [curamd64-setuptools-job-02] `-- Installing py311-sqlparse-0.5.5... [curamd64-setuptools-job-02] `-- Extracting py311-sqlparse-0.5.5: .......... done [curamd64-setuptools-job-02] Extracting py311-django42-4.2.30: .......... done ===== Message from py311-django42-4.2.30: -- ===> NOTICE: This port is deprecated; you may wish to reconsider installing it: Django 4.2 is now in Extended Support, receives security fixes only and will reach End-Of-Life in April 2026. Upgrade to a later Django version. See https://www.djangoproject.com/download/. It is scheduled to be removed on or after 2026-05-31. ===> py311-django-contrib-comments-2.2.0_3 depends on package: py311-django42>=2.2 - found ===> Returning to build of py311-django-contrib-comments-2.2.0_3 ===> py311-django-contrib-comments-2.2.0_3 depends on file: /usr/local/bin/python3.11 - found =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Staging for py311-django-contrib-comments-2.2.0_3 ===> Generating temporary packing list /usr/local/lib/python3.11/site-packages/setuptools/_distutils/dist.py:287: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/local/lib/python3.11/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running install /usr/local/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing django_contrib_comments.egg-info/PKG-INFO writing dependency_links to django_contrib_comments.egg-info/dependency_links.txt writing requirements to django_contrib_comments.egg-info/requires.txt writing top-level names to django_contrib_comments.egg-info/top_level.txt reading manifest file 'django_contrib_comments.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE.txt' writing manifest file 'django_contrib_comments.egg-info/SOURCES.txt' /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.fy_NL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.fy_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_comments.locale.fy_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_comments.locale.fy_NL.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.fy_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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.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_comments.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_comments.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.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) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_comments.templates.comments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.templates.comments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.templates.comments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.templates.comments' to be distributed and are already explicitly excluding 'django_comments.templates.comments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) running install_lib creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/__init__.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/abstracts.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/admin.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/apps.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/compat.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/feeds.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/forms.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/managers.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/models.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/moderation.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/signals.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments copying build/lib/django_comments/urls.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management copying build/lib/django_comments/management/__init__.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management/commands copying build/lib/django_comments/management/commands/__init__.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management/commands copying build/lib/django_comments/management/commands/delete_stale_comments.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management/commands creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/0001_initial.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/0002_update_user_email_field_length.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/0003_add_submit_date_index.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/0004_add_object_pk_is_removed_index.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/__init__.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templatetags copying build/lib/django_comments/templatetags/__init__.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templatetags copying build/lib/django_comments/templatetags/comments.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templatetags creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views copying build/lib/django_comments/views/__init__.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views copying build/lib/django_comments/views/comments.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views copying build/lib/django_comments/views/moderation.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views copying build/lib/django_comments/views/utils.py -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/af creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/af/LC_MESSAGES copying build/lib/django_comments/locale/af/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/af/LC_MESSAGES copying build/lib/django_comments/locale/af/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/af/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ar creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ar/LC_MESSAGES copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ar/LC_MESSAGES copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ar/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/az creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/az/LC_MESSAGES copying build/lib/django_comments/locale/az/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/az/LC_MESSAGES copying build/lib/django_comments/locale/az/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/az/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/be creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/be/LC_MESSAGES copying build/lib/django_comments/locale/be/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/be/LC_MESSAGES copying build/lib/django_comments/locale/be/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/be/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bg creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bg/LC_MESSAGES copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bg/LC_MESSAGES copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bg/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bn creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bn/LC_MESSAGES copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bn/LC_MESSAGES copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/br creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/br/LC_MESSAGES copying build/lib/django_comments/locale/br/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/br/LC_MESSAGES copying build/lib/django_comments/locale/br/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/br/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bs creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bs/LC_MESSAGES copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bs/LC_MESSAGES copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/bs/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ca creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ca/LC_MESSAGES copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ca/LC_MESSAGES copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ca/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cs creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cs/LC_MESSAGES copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cs/LC_MESSAGES copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cs/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cy creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cy/LC_MESSAGES copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cy/LC_MESSAGES copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/cy/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/da creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/da/LC_MESSAGES copying build/lib/django_comments/locale/da/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/da/LC_MESSAGES copying build/lib/django_comments/locale/da/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/da/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/de creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/de/LC_MESSAGES copying build/lib/django_comments/locale/de/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/de/LC_MESSAGES copying build/lib/django_comments/locale/de/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/de/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/el creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/el/LC_MESSAGES copying build/lib/django_comments/locale/el/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/el/LC_MESSAGES copying build/lib/django_comments/locale/el/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/el/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en/LC_MESSAGES copying build/lib/django_comments/locale/en/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en/LC_MESSAGES copying build/lib/django_comments/locale/en/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en_GB creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en_GB/LC_MESSAGES copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en_GB/LC_MESSAGES copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/en_GB/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eo creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eo/LC_MESSAGES copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eo/LC_MESSAGES copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eo/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es/LC_MESSAGES copying build/lib/django_comments/locale/es/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es/LC_MESSAGES copying build/lib/django_comments/locale/es/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_AR creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_AR/LC_MESSAGES copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_AR/LC_MESSAGES copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_AR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_MX creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_MX/LC_MESSAGES copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_MX/LC_MESSAGES copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/es_MX/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/et creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/et/LC_MESSAGES copying build/lib/django_comments/locale/et/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/et/LC_MESSAGES copying build/lib/django_comments/locale/et/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/et/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eu creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eu/LC_MESSAGES copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eu/LC_MESSAGES copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/eu/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fa creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fa/LC_MESSAGES copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fa/LC_MESSAGES copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fa/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fi creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fi/LC_MESSAGES copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fi/LC_MESSAGES copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fi/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fr creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fr/LC_MESSAGES copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fr/LC_MESSAGES copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fy_NL creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fy_NL/LC_MESSAGES copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fy_NL/LC_MESSAGES copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/fy_NL/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ga creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ga/LC_MESSAGES copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ga/LC_MESSAGES copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ga/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gd creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gd/LC_MESSAGES copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gd/LC_MESSAGES copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gd/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gl creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gl/LC_MESSAGES copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gl/LC_MESSAGES copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/gl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/he creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/he/LC_MESSAGES copying build/lib/django_comments/locale/he/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/he/LC_MESSAGES copying build/lib/django_comments/locale/he/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/he/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hi creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hi/LC_MESSAGES copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hi/LC_MESSAGES copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hi/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hr creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hr/LC_MESSAGES copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hr/LC_MESSAGES copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hu creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hu/LC_MESSAGES copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hu/LC_MESSAGES copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/hu/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ia creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ia/LC_MESSAGES copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ia/LC_MESSAGES copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ia/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/id creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/id/LC_MESSAGES copying build/lib/django_comments/locale/id/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/id/LC_MESSAGES copying build/lib/django_comments/locale/id/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/id/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/is creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/is/LC_MESSAGES copying build/lib/django_comments/locale/is/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/is/LC_MESSAGES copying build/lib/django_comments/locale/is/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/is/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/it creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/it/LC_MESSAGES copying build/lib/django_comments/locale/it/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/it/LC_MESSAGES copying build/lib/django_comments/locale/it/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/it/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ja creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ja/LC_MESSAGES copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ja/LC_MESSAGES copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ja/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ka creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ka/LC_MESSAGES copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ka/LC_MESSAGES copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ka/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kk creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kk/LC_MESSAGES copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kk/LC_MESSAGES copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kk/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/km creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/km/LC_MESSAGES copying build/lib/django_comments/locale/km/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/km/LC_MESSAGES copying build/lib/django_comments/locale/km/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/km/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kn creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kn/LC_MESSAGES copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kn/LC_MESSAGES copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/kn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ko creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ko/LC_MESSAGES copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ko/LC_MESSAGES copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ko/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lt creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lt/LC_MESSAGES copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lt/LC_MESSAGES copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lt/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lv creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lv/LC_MESSAGES copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lv/LC_MESSAGES copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/lv/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mk creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mk/LC_MESSAGES copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mk/LC_MESSAGES copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mk/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ml creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ml/LC_MESSAGES copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ml/LC_MESSAGES copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ml/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mn creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mn/LC_MESSAGES copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mn/LC_MESSAGES copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/mn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nb creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nb/LC_MESSAGES copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nb/LC_MESSAGES copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nb/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ne creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ne/LC_MESSAGES copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ne/LC_MESSAGES copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ne/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nl creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nl/LC_MESSAGES copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nl/LC_MESSAGES copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nn creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nn/LC_MESSAGES copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nn/LC_MESSAGES copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/nn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pa creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pa/LC_MESSAGES copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pa/LC_MESSAGES copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pa/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pl creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pl/LC_MESSAGES copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pl/LC_MESSAGES copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt/LC_MESSAGES copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt/LC_MESSAGES copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt_BR creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt_BR/LC_MESSAGES copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt_BR/LC_MESSAGES copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/pt_BR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ro creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ro/LC_MESSAGES copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ro/LC_MESSAGES copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ro/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ru creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ru/LC_MESSAGES copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ru/LC_MESSAGES copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ru/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sk creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sk/LC_MESSAGES copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sk/LC_MESSAGES copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sk/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sl creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sl/LC_MESSAGES copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sl/LC_MESSAGES copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sq creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sq/LC_MESSAGES copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sq/LC_MESSAGES copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sq/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr/LC_MESSAGES copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr/LC_MESSAGES copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr_Latn creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sv creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sv/LC_MESSAGES copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sv/LC_MESSAGES copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sv/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sw creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sw/LC_MESSAGES copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sw/LC_MESSAGES copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/sw/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ta creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ta/LC_MESSAGES copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ta/LC_MESSAGES copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ta/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/te creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/te/LC_MESSAGES copying build/lib/django_comments/locale/te/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/te/LC_MESSAGES copying build/lib/django_comments/locale/te/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/te/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/th creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/th/LC_MESSAGES copying build/lib/django_comments/locale/th/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/th/LC_MESSAGES copying build/lib/django_comments/locale/th/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/th/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tr creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tr/LC_MESSAGES copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tr/LC_MESSAGES copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tt creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tt/LC_MESSAGES copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tt/LC_MESSAGES copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/tt/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/uk creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/uk/LC_MESSAGES copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/uk/LC_MESSAGES copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/uk/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ur creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ur/LC_MESSAGES copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ur/LC_MESSAGES copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/ur/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/vi creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/vi/LC_MESSAGES copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/vi/LC_MESSAGES copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/vi/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hans creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hant creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates creating /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/400-debug.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/approve.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/approved.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/base.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/delete.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/deleted.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/flag.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/flagged.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/form.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/list.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/posted.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/preview.html -> /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templates/comments byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/abstracts.py to abstracts.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/compat.py to compat.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/feeds.py to feeds.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/managers.py to managers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/moderation.py to moderation.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/signals.py to signals.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/urls.py to urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/management/commands/delete_stale_comments.py to delete_stale_comments.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations/0002_update_user_email_field_length.py to 0002_update_user_email_field_length.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations/0003_add_submit_date_index.py to 0003_add_submit_date_index.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations/0004_add_object_pk_is_removed_index.py to 0004_add_object_pk_is_removed_index.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/templatetags/comments.py to comments.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views/comments.py to comments.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views/moderation.py to moderation.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_comments/views/utils.py to utils.cpython-311.pyc writing byte-compilation script '/tmp/tmpznpyljhx.py' /usr/local/bin/python3.11 /tmp/tmpznpyljhx.py removing /tmp/tmpznpyljhx.py running install_egg_info Copying django_contrib_comments.egg-info to /wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/stage/usr/local/lib/python3.11/site-packages/django_contrib_comments-2.2.0-py3.11.egg-info running install_scripts writing list of installed files to '/wrkdirs/usr/ports/www/py-django-contrib-comments/work-py311/.PLIST.pymodtmp' ====> Compressing man pages (compress-man) =========================================================================== =================================================== ===== env: 'PKG_NOTES=build_timestamp ports_top_git_hash ports_top_checkout_unclean port_git_hash port_checkout_unclean built_by' 'PKG_NOTE_build_timestamp=2026-06-01T20:48:08+0000' 'PKG_NOTE_ports_top_git_hash=a8b187544' 'PKG_NOTE_ports_top_checkout_unclean=yes' 'PKG_NOTE_port_git_hash=a8b187544' 'PKG_NOTE_port_checkout_unclean=no' 'PKG_NOTE_built_by=poudriere-git-3.4.4' NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Building packages for py311-django-contrib-comments-2.2.0_3 ===> Building py311-django-contrib-comments-2.2.0_3 =========================================================================== =>> Cleaning up wrkdir ===> Cleaning for py311-django-contrib-comments-2.2.0_3 build of www/py-django-contrib-comments@py311 | py311-django-contrib-comments-2.2.0_3 ended at Tue Jun 2 05:53:04 JST 2026 build time: 00:08:08