=> Bootstrap dependency digest>=20211023: found digest-20220214 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Building for py39-django-countries-7.5.1 (cd /tmp/www/py-django-countries/work/django-countries-7.5.1/ && /usr/bin/env USETOOLS=no PTHREAD_CFLAGS=\ -pthread\ PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS= PTHREADBASE=/usr DL_CFLAGS=\ -pthread\ DL_LDFLAGS=\ -pthread DL_LIBS= PYTHON=/usr/pkg/bin/python3.9 CC=gcc CFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.9 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.9 CXX=c++ CXXFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.9 COMPILER_RPATH_FLAG=-Wl,-R F77=gfortran FC=gfortran FFLAGS=-O LANG=C LC_ALL=C LC_COLLATE=C LC_CTYPE=C LC_MESSAGES=C LC_MONETARY=C LC_NUMERIC=C LC_TIME=C LDFLAGS=-Wl,-zrelro\ -L/usr/lib\ -Wl,-R/usr/lib\ -Wl,-R/usr/pkg/lib LINKER_RPATH_FLAG=-R PATH=/tmp/www/py-django-countries/work/.cwrapper/bin:/tmp/www/py-django-countries/work/.buildlink/bin:/tmp/www/py-django-countries/work/.tools/bin:/usr/pkg/bin:/usr/bin:/bin:/usr/pkg/bin:/usr/local/bin:/usr/pkg/bin:/usr/X11R7/bin PREFIX=/usr/pkg MAKELEVEL=0 CONFIG_SITE= PKG_SYSCONFDIR=/usr/pkg/etc CPP=cpp CXXCPP=cpp HOME=/tmp/www/py-django-countries/work/.home CWRAPPERS_CONFIG_DIR=/tmp/www/py-django-countries/work/.cwrapper/config CPP=cpp LOCALBASE=/usr/pkg X11BASE=/usr/X11R7 PKGMANDIR=man PKGINFODIR=info PKGGNUDIR=gnu/ MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL_MAN=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL=/usr/bin/install BSD_INSTALL_PROGRAM_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_MAN_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_GAME=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 2555 BSD_INSTALL_GAME_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 664 BSD_INSTALL_GAME_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 775 INSTALL_INFO= MAKEINFO=/tmp/www/py-django-countries/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/www/py-django-countries/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/www/py-django-countries/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/www/py-django-countries/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/www/py-django-countries/work/.buildlink/lib/pkgconfig:/tmp/www/py-django-countries/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/www/py-django-countries/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/www/py-django-countries/work/.cwrapper/config /usr/pkg/bin/python3.9 setup.py build -j4) running build running build_py creating build creating build/lib creating build/lib/django_countries copying django_countries/__init__.py -> build/lib/django_countries copying django_countries/base.py -> build/lib/django_countries copying django_countries/conf.py -> build/lib/django_countries copying django_countries/data.py -> build/lib/django_countries copying django_countries/fields.py -> build/lib/django_countries copying django_countries/filters.py -> build/lib/django_countries copying django_countries/ioc_data.py -> build/lib/django_countries copying django_countries/makesprite.py -> build/lib/django_countries copying django_countries/models.py -> build/lib/django_countries copying django_countries/release.py -> build/lib/django_countries copying django_countries/serializer_fields.py -> build/lib/django_countries copying django_countries/serializers.py -> build/lib/django_countries copying django_countries/widgets.py -> build/lib/django_countries creating build/lib/django_countries/graphql copying django_countries/graphql/__init__.py -> build/lib/django_countries/graphql copying django_countries/graphql/types.py -> build/lib/django_countries/graphql creating build/lib/django_countries/templatetags copying django_countries/templatetags/__init__.py -> build/lib/django_countries/templatetags copying django_countries/templatetags/countries.py -> build/lib/django_countries/templatetags creating build/lib/django_countries/tests copying django_countries/tests/__init__.py -> build/lib/django_countries/tests copying django_countries/tests/apps.py -> build/lib/django_countries/tests copying django_countries/tests/custom_countries.py -> build/lib/django_countries/tests copying django_countries/tests/forms.py -> build/lib/django_countries/tests copying django_countries/tests/models.py -> build/lib/django_countries/tests copying django_countries/tests/settings.py -> build/lib/django_countries/tests copying django_countries/tests/settings_noi18n.py -> build/lib/django_countries/tests copying django_countries/tests/test_admin_filters.py -> build/lib/django_countries/tests copying django_countries/tests/test_countries.py -> build/lib/django_countries/tests copying django_countries/tests/test_drf.py -> build/lib/django_countries/tests copying django_countries/tests/test_fields.py -> build/lib/django_countries/tests copying django_countries/tests/test_settings.py -> build/lib/django_countries/tests copying django_countries/tests/test_tags.py -> build/lib/django_countries/tests copying django_countries/tests/test_widgets.py -> build/lib/django_countries/tests creating build/lib/django_countries/tests/graphql copying django_countries/tests/graphql/__init__.py -> build/lib/django_countries/tests/graphql copying django_countries/tests/graphql/schema.py -> build/lib/django_countries/tests/graphql copying django_countries/tests/graphql/test_country_type.py -> build/lib/django_countries/tests/graphql copying django_countries/tests/graphql/test_model.py -> build/lib/django_countries/tests/graphql running egg_info writing django_countries.egg-info/PKG-INFO writing dependency_links to django_countries.egg-info/dependency_links.txt writing requirements to django_countries.egg-info/requires.txt writing top-level names to django_countries.egg-info/top_level.txt reading manifest file 'django_countries.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'tox.ini' warning: no previously-included files found matching '.isort.cfg' warning: no previously-included files found matching '.pre-commit-config.yaml' no previously-included directories found matching '.tx' adding license file 'LICENSE' writing manifest file 'django_countries.egg-info/SOURCES.txt' /usr/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_countries.locale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_countries.locale' to be distributed and are already explicitly excluding 'django_countries.locale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.eu_ES.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.eu_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_countries.locale.eu_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_countries.locale.eu_ES.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.eu_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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.he_IL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.he_IL.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_countries.locale.he_IL.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_countries.locale.he_IL.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.he_IL.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.hy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_countries.locale.hy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_countries.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.ko_KR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.ko_KR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_countries.locale.ko_KR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_countries.locale.ko_KR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.ko_KR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.pt_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_countries.locale.pt_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_countries.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.pt_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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.sr_Latn_BA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.sr_Latn_BA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_countries.locale.sr_Latn_BA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_countries.locale.sr_Latn_BA.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.sr_Latn_BA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.tr_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_countries.locale.tr_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_countries.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.tr_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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_countries.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_countries.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.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_countries.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_countries.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_countries.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/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_countries.static.flags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_countries.static.flags' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_countries.static.flags' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_countries.static.flags' to be distributed and are already explicitly excluding 'django_countries.static.flags' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) copying django_countries/py.typed -> build/lib/django_countries creating build/lib/django_countries/locale creating build/lib/django_countries/locale/af creating build/lib/django_countries/locale/af/LC_MESSAGES copying django_countries/locale/af/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/af/LC_MESSAGES copying django_countries/locale/af/LC_MESSAGES/django.po -> build/lib/django_countries/locale/af/LC_MESSAGES creating build/lib/django_countries/locale/ar creating build/lib/django_countries/locale/ar/LC_MESSAGES copying django_countries/locale/ar/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/ar/LC_MESSAGES copying django_countries/locale/ar/LC_MESSAGES/django.po -> build/lib/django_countries/locale/ar/LC_MESSAGES creating build/lib/django_countries/locale/bg creating build/lib/django_countries/locale/bg/LC_MESSAGES copying django_countries/locale/bg/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/bg/LC_MESSAGES copying django_countries/locale/bg/LC_MESSAGES/django.po -> build/lib/django_countries/locale/bg/LC_MESSAGES creating build/lib/django_countries/locale/ca creating build/lib/django_countries/locale/ca/LC_MESSAGES copying django_countries/locale/ca/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/ca/LC_MESSAGES copying django_countries/locale/ca/LC_MESSAGES/django.po -> build/lib/django_countries/locale/ca/LC_MESSAGES creating build/lib/django_countries/locale/cs creating build/lib/django_countries/locale/cs/LC_MESSAGES copying django_countries/locale/cs/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/cs/LC_MESSAGES copying django_countries/locale/cs/LC_MESSAGES/django.po -> build/lib/django_countries/locale/cs/LC_MESSAGES creating build/lib/django_countries/locale/da creating build/lib/django_countries/locale/da/LC_MESSAGES copying django_countries/locale/da/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/da/LC_MESSAGES copying django_countries/locale/da/LC_MESSAGES/django.po -> build/lib/django_countries/locale/da/LC_MESSAGES creating build/lib/django_countries/locale/de creating build/lib/django_countries/locale/de/LC_MESSAGES copying django_countries/locale/de/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/de/LC_MESSAGES copying django_countries/locale/de/LC_MESSAGES/django.po -> build/lib/django_countries/locale/de/LC_MESSAGES creating build/lib/django_countries/locale/el creating build/lib/django_countries/locale/el/LC_MESSAGES copying django_countries/locale/el/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/el/LC_MESSAGES copying django_countries/locale/el/LC_MESSAGES/django.po -> build/lib/django_countries/locale/el/LC_MESSAGES creating build/lib/django_countries/locale/en@test creating build/lib/django_countries/locale/en@test/LC_MESSAGES copying django_countries/locale/en@test/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/en@test/LC_MESSAGES copying django_countries/locale/en@test/LC_MESSAGES/django.po -> build/lib/django_countries/locale/en@test/LC_MESSAGES creating build/lib/django_countries/locale/eo creating build/lib/django_countries/locale/eo/LC_MESSAGES copying django_countries/locale/eo/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/eo/LC_MESSAGES copying django_countries/locale/eo/LC_MESSAGES/django.po -> build/lib/django_countries/locale/eo/LC_MESSAGES creating build/lib/django_countries/locale/es creating build/lib/django_countries/locale/es/LC_MESSAGES copying django_countries/locale/es/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/es/LC_MESSAGES copying django_countries/locale/es/LC_MESSAGES/django.po -> build/lib/django_countries/locale/es/LC_MESSAGES creating build/lib/django_countries/locale/et creating build/lib/django_countries/locale/et/LC_MESSAGES copying django_countries/locale/et/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/et/LC_MESSAGES copying django_countries/locale/et/LC_MESSAGES/django.po -> build/lib/django_countries/locale/et/LC_MESSAGES creating build/lib/django_countries/locale/eu creating build/lib/django_countries/locale/eu/LC_MESSAGES copying django_countries/locale/eu/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/eu/LC_MESSAGES copying django_countries/locale/eu/LC_MESSAGES/django.po -> build/lib/django_countries/locale/eu/LC_MESSAGES creating build/lib/django_countries/locale/eu_ES creating build/lib/django_countries/locale/eu_ES/LC_MESSAGES copying django_countries/locale/eu_ES/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/eu_ES/LC_MESSAGES copying django_countries/locale/eu_ES/LC_MESSAGES/django.po -> build/lib/django_countries/locale/eu_ES/LC_MESSAGES creating build/lib/django_countries/locale/fa creating build/lib/django_countries/locale/fa/LC_MESSAGES copying django_countries/locale/fa/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/fa/LC_MESSAGES copying django_countries/locale/fa/LC_MESSAGES/django.po -> build/lib/django_countries/locale/fa/LC_MESSAGES creating build/lib/django_countries/locale/fi creating build/lib/django_countries/locale/fi/LC_MESSAGES copying django_countries/locale/fi/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/fi/LC_MESSAGES copying django_countries/locale/fi/LC_MESSAGES/django.po -> build/lib/django_countries/locale/fi/LC_MESSAGES creating build/lib/django_countries/locale/fr creating build/lib/django_countries/locale/fr/LC_MESSAGES copying django_countries/locale/fr/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/fr/LC_MESSAGES copying django_countries/locale/fr/LC_MESSAGES/django.po -> build/lib/django_countries/locale/fr/LC_MESSAGES creating build/lib/django_countries/locale/he creating build/lib/django_countries/locale/he/LC_MESSAGES copying django_countries/locale/he/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/he/LC_MESSAGES copying django_countries/locale/he/LC_MESSAGES/django.po -> build/lib/django_countries/locale/he/LC_MESSAGES creating build/lib/django_countries/locale/he_IL creating build/lib/django_countries/locale/he_IL/LC_MESSAGES copying django_countries/locale/he_IL/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/he_IL/LC_MESSAGES copying django_countries/locale/he_IL/LC_MESSAGES/django.po -> build/lib/django_countries/locale/he_IL/LC_MESSAGES creating build/lib/django_countries/locale/hr creating build/lib/django_countries/locale/hr/LC_MESSAGES copying django_countries/locale/hr/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/hr/LC_MESSAGES copying django_countries/locale/hr/LC_MESSAGES/django.po -> build/lib/django_countries/locale/hr/LC_MESSAGES creating build/lib/django_countries/locale/hu creating build/lib/django_countries/locale/hu/LC_MESSAGES copying django_countries/locale/hu/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/hu/LC_MESSAGES copying django_countries/locale/hu/LC_MESSAGES/django.po -> build/lib/django_countries/locale/hu/LC_MESSAGES creating build/lib/django_countries/locale/hy creating build/lib/django_countries/locale/hy/LC_MESSAGES copying django_countries/locale/hy/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/hy/LC_MESSAGES copying django_countries/locale/hy/LC_MESSAGES/django.po -> build/lib/django_countries/locale/hy/LC_MESSAGES creating build/lib/django_countries/locale/it creating build/lib/django_countries/locale/it/LC_MESSAGES copying django_countries/locale/it/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/it/LC_MESSAGES copying django_countries/locale/it/LC_MESSAGES/django.po -> build/lib/django_countries/locale/it/LC_MESSAGES creating build/lib/django_countries/locale/ja creating build/lib/django_countries/locale/ja/LC_MESSAGES copying django_countries/locale/ja/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/ja/LC_MESSAGES copying django_countries/locale/ja/LC_MESSAGES/django.po -> build/lib/django_countries/locale/ja/LC_MESSAGES creating build/lib/django_countries/locale/ko_KR creating build/lib/django_countries/locale/ko_KR/LC_MESSAGES copying django_countries/locale/ko_KR/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/ko_KR/LC_MESSAGES copying django_countries/locale/ko_KR/LC_MESSAGES/django.po -> build/lib/django_countries/locale/ko_KR/LC_MESSAGES creating build/lib/django_countries/locale/lt creating build/lib/django_countries/locale/lt/LC_MESSAGES copying django_countries/locale/lt/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/lt/LC_MESSAGES copying django_countries/locale/lt/LC_MESSAGES/django.po -> build/lib/django_countries/locale/lt/LC_MESSAGES creating build/lib/django_countries/locale/lv creating build/lib/django_countries/locale/lv/LC_MESSAGES copying django_countries/locale/lv/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/lv/LC_MESSAGES copying django_countries/locale/lv/LC_MESSAGES/django.po -> build/lib/django_countries/locale/lv/LC_MESSAGES creating build/lib/django_countries/locale/mn creating build/lib/django_countries/locale/mn/LC_MESSAGES copying django_countries/locale/mn/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/mn/LC_MESSAGES copying django_countries/locale/mn/LC_MESSAGES/django.po -> build/lib/django_countries/locale/mn/LC_MESSAGES creating build/lib/django_countries/locale/nb creating build/lib/django_countries/locale/nb/LC_MESSAGES copying django_countries/locale/nb/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/nb/LC_MESSAGES copying django_countries/locale/nb/LC_MESSAGES/django.po -> build/lib/django_countries/locale/nb/LC_MESSAGES creating build/lib/django_countries/locale/nl creating build/lib/django_countries/locale/nl/LC_MESSAGES copying django_countries/locale/nl/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/nl/LC_MESSAGES copying django_countries/locale/nl/LC_MESSAGES/django.po -> build/lib/django_countries/locale/nl/LC_MESSAGES creating build/lib/django_countries/locale/pl creating build/lib/django_countries/locale/pl/LC_MESSAGES copying django_countries/locale/pl/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/pl/LC_MESSAGES copying django_countries/locale/pl/LC_MESSAGES/django.po -> build/lib/django_countries/locale/pl/LC_MESSAGES creating build/lib/django_countries/locale/pt_BR creating build/lib/django_countries/locale/pt_BR/LC_MESSAGES copying django_countries/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/pt_BR/LC_MESSAGES copying django_countries/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django_countries/locale/pt_BR/LC_MESSAGES creating build/lib/django_countries/locale/pt_PT creating build/lib/django_countries/locale/pt_PT/LC_MESSAGES copying django_countries/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/pt_PT/LC_MESSAGES copying django_countries/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/django_countries/locale/pt_PT/LC_MESSAGES creating build/lib/django_countries/locale/ro creating build/lib/django_countries/locale/ro/LC_MESSAGES copying django_countries/locale/ro/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/ro/LC_MESSAGES copying django_countries/locale/ro/LC_MESSAGES/django.po -> build/lib/django_countries/locale/ro/LC_MESSAGES creating build/lib/django_countries/locale/ru creating build/lib/django_countries/locale/ru/LC_MESSAGES copying django_countries/locale/ru/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/ru/LC_MESSAGES copying django_countries/locale/ru/LC_MESSAGES/django.po -> build/lib/django_countries/locale/ru/LC_MESSAGES creating build/lib/django_countries/locale/sk creating build/lib/django_countries/locale/sk/LC_MESSAGES copying django_countries/locale/sk/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/sk/LC_MESSAGES copying django_countries/locale/sk/LC_MESSAGES/django.po -> build/lib/django_countries/locale/sk/LC_MESSAGES creating build/lib/django_countries/locale/sl creating build/lib/django_countries/locale/sl/LC_MESSAGES copying django_countries/locale/sl/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/sl/LC_MESSAGES copying django_countries/locale/sl/LC_MESSAGES/django.po -> build/lib/django_countries/locale/sl/LC_MESSAGES creating build/lib/django_countries/locale/sr creating build/lib/django_countries/locale/sr/LC_MESSAGES copying django_countries/locale/sr/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/sr/LC_MESSAGES copying django_countries/locale/sr/LC_MESSAGES/django.po -> build/lib/django_countries/locale/sr/LC_MESSAGES creating build/lib/django_countries/locale/sr@latin creating build/lib/django_countries/locale/sr@latin/LC_MESSAGES copying django_countries/locale/sr@latin/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/sr@latin/LC_MESSAGES copying django_countries/locale/sr@latin/LC_MESSAGES/django.po -> build/lib/django_countries/locale/sr@latin/LC_MESSAGES creating build/lib/django_countries/locale/sr_Latn creating build/lib/django_countries/locale/sr_Latn/LC_MESSAGES copying django_countries/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/sr_Latn/LC_MESSAGES copying django_countries/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django_countries/locale/sr_Latn/LC_MESSAGES creating build/lib/django_countries/locale/sr_Latn_BA creating build/lib/django_countries/locale/sr_Latn_BA/LC_MESSAGES copying django_countries/locale/sr_Latn_BA/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/sr_Latn_BA/LC_MESSAGES copying django_countries/locale/sr_Latn_BA/LC_MESSAGES/django.po -> build/lib/django_countries/locale/sr_Latn_BA/LC_MESSAGES creating build/lib/django_countries/locale/sv creating build/lib/django_countries/locale/sv/LC_MESSAGES copying django_countries/locale/sv/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/sv/LC_MESSAGES copying django_countries/locale/sv/LC_MESSAGES/django.po -> build/lib/django_countries/locale/sv/LC_MESSAGES creating build/lib/django_countries/locale/tr_TR creating build/lib/django_countries/locale/tr_TR/LC_MESSAGES copying django_countries/locale/tr_TR/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/tr_TR/LC_MESSAGES copying django_countries/locale/tr_TR/LC_MESSAGES/django.po -> build/lib/django_countries/locale/tr_TR/LC_MESSAGES creating build/lib/django_countries/locale/uk creating build/lib/django_countries/locale/uk/LC_MESSAGES copying django_countries/locale/uk/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/uk/LC_MESSAGES copying django_countries/locale/uk/LC_MESSAGES/django.po -> build/lib/django_countries/locale/uk/LC_MESSAGES creating build/lib/django_countries/locale/zh_CN creating build/lib/django_countries/locale/zh_CN/LC_MESSAGES copying django_countries/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/zh_CN/LC_MESSAGES copying django_countries/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/django_countries/locale/zh_CN/LC_MESSAGES creating build/lib/django_countries/locale/zh_Hans creating build/lib/django_countries/locale/zh_Hans/LC_MESSAGES copying django_countries/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/zh_Hans/LC_MESSAGES copying django_countries/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django_countries/locale/zh_Hans/LC_MESSAGES creating build/lib/django_countries/locale/zh_Hant creating build/lib/django_countries/locale/zh_Hant/LC_MESSAGES copying django_countries/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django_countries/locale/zh_Hant/LC_MESSAGES copying django_countries/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django_countries/locale/zh_Hant/LC_MESSAGES creating build/lib/django_countries/static creating build/lib/django_countries/static/flags copying django_countries/static/flags/__.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ad.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ae.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/af.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ag.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ai.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/al.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/am.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ao.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/aq.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ar.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/as.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/at.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/au.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/aw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ax.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/az.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ba.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bb.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bd.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/be.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bh.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bi.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bj.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bl.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bo.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bq.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/br.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bs.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bt.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bv.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/by.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/bz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ca.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cc.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cd.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ch.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ci.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ck.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cl.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/co.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cv.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cx.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cy.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/cz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/de.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/dj.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/dk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/dm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/do.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/dz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ec.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ee.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/eg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/eh.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/er.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/es.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/et.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/eu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/fi.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/fj.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/fk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/fm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/fo.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/fr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ga.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gb.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gd.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ge.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gh.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gi.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gl.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gp.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gq.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gs.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gt.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/gy.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/hk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/hm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/hn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/hr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ht.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/hu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/id.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ie.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/il.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/im.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/in.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/io.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/iq.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ir.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/is.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/it.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/je.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/jm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/jo.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/jp.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ke.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/kg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/kh.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ki.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/km.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/kn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/kp.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/kr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/kw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ky.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/kz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/la.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/lb.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/lc.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/li.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/lk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/lr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ls.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/lt.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/lu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/lv.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ly.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ma.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mc.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/md.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/me.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mh.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ml.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mo.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mp.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mq.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ms.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mt.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mv.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mx.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/my.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/mz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/na.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/nc.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ne.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/nf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ng.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ni.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/nl.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/no.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/np.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/nr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/nu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/nz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/om.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pa.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pe.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ph.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pl.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ps.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pt.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/pw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/py.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/qa.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/re.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ro.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/rs.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ru.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/rw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sa.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sb.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sc.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sd.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/se.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sh.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/si.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sj.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sl.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/so.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sprite-hq.css -> build/lib/django_countries/static/flags copying django_countries/static/flags/sprite-hq.png -> build/lib/django_countries/static/flags copying django_countries/static/flags/sprite.css -> build/lib/django_countries/static/flags copying django_countries/static/flags/sprite.png -> build/lib/django_countries/static/flags copying django_countries/static/flags/sr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ss.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/st.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sv.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sx.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sy.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/sz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tc.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/td.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/th.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tj.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tl.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/to.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tr.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tt.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tv.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tw.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/tz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ua.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ug.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/um.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/us.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/uy.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/uz.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/va.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/vc.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ve.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/vg.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/vi.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/vn.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/vu.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/wf.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ws.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/xk.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/ye.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/yt.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/za.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/zm.gif -> build/lib/django_countries/static/flags copying django_countries/static/flags/zw.gif -> build/lib/django_countries/static/flags